Product · Entities
LMTOne entity, resolved — with the filing behind every number.
A company appears once in Forum Atlas, not once per sector, and every financial fact attached to it names the filing it was read from. Below is a published entity, read live: its verified facts with their SEC accession numbers, and its relationships split by whether they pass the gate that decides what the product is allowed to draw.
read from the published set 2026-10-21 09:37 UTC · entity lockheed-martin
Verified facts
Every number names its filing.
Each row was read from a filing and stored with the form type and the accession number of the document it came from. Follow the accession and you are looking at the same page we were.
6
Verified facts on this entity
6
Shown below
published payload caps at 12
FY2025
Reporting period
as stored on the facts
| Concept | Value | Period | Form | Accession |
|---|---|---|---|---|
| Shares outstanding | 230,080,240 shares | FY2025 | 10-K | 0001628280-26-004195 |
| Stockholders' equity | 6,721,000,000 USD$6.721B | FY2025 | 10-K | 0001628280-26-004195 |
| Total liabilities | 53,119,000,000 USD$53.119B | FY2025 | 10-K | 0001628280-26-004195 |
| Total assets | 59,840,000,000 USD$59.84B | FY2025 | 10-K | 0001628280-26-004195 |
| Net income | 5,017,000,000 USD$5.017B | FY2025 | 10-K | 0001628280-26-004195 |
| Revenue | 75,048,000,000 USD$75.048B | FY2025 | 10-K | 0001628280-26-004195 |
verified facts as stored, with form type and accession · counted 2026-10-21 09:37 UTC
A fact reaches this table only if it is marked verified and is not flagged as scale- or period-suspect. Facts that fail either check stay out of the dossier rather than being shown with a caveat — the caveat is what people skip.
Relationships
1 of 23 relationships pass the gate.
A relationship is drawn on the strength of where it came from, not on a confidence score. The split below is what that gate produced on this entity.
- Passes the gate · drawn
- 1
- 4.3% of stored edges. Either the relationship comes from an identifier registry, or a model extracted it and it has since been marked verified with every source document behind it still resolving.
- Candidate · held back
- 22
- 95.7% of stored edges. Extracted, stored, and failing the gate — so they are not drawn on the dossier, not exported, and not citable.
stored relationships by trust-gate outcome · counted 2026-10-21 09:37 UTC
What the gate is. A relationship carried by an identifier registry — an SEC filer mapping, a GLEIF LEI, a Wikidata QID — is drawn on that provenance. A relationship a model extracted from a document is drawn only once it has been marked verified and every source document behind it still resolves; a cited document that has been deleted cannot be shown to you, so the edge is unsubstantiable and comes down with it. Everything else is stored and not drawn: counted here, not on the dossier, not in an export, not available to cite.
Why the small number is printed. A gate that passes almost everything is not a gate. On this entity 23 relationships are stored and 1 cleared the bar. That ratio is the honest state of relationship extraction here, and hiding it would make the figure meaningless the first time a reader checked it.
The candidate count is a count of stored rows that fail the read-path predicate. It is not a co-mention ring: that read has no rollup behind it yet and is not run on this page, so no co-mention figure appears.
The three states
- Verified
- Registry provenance, or marked verified with its documents intact. Drawn, exportable, citable.
- Candidate
- Extracted and stored, gate not met. Counted here, drawn nowhere.
- Withheld
- Failed validation outright. Removed from the deliverable and counted in the published withhold rate.
Citation discipline sets out all three in full.
Entity dossiers are readable on the free tier; cross-sector coverage scales by tier.
Start freeSee pricing