Triple
T1523723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Marietta |
E32286
|
entity |
| Predicate | reasonForStatus |
P30133
|
FINISHED |
| Object | merged to form Lockheed Martin |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: merged to form Lockheed Martin | Statement: [Martin Marietta, reasonForStatus, merged to form Lockheed Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForStatus Context triple: [Martin Marietta, reasonForStatus, merged to form Lockheed Martin]
-
A.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
reasonForException
Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
-
C.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
D.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a93d462f208190b27ef5cd631bce12 |
completed | March 5, 2026, 8:22 a.m. |
Created at: March 4, 2026, 7:26 p.m.