Triple
T1181382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIIE |
E25143
|
entity |
| Predicate | failureDetail |
P21234
|
FINISHED |
| Object | one launch failed due to Centaur upper stage issue |
—
|
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: one launch failed due to Centaur upper stage issue | Statement: [Titan IIIE, failureDetail, one launch failed due to Centaur upper stage issue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureDetail Context triple: [Titan IIIE, failureDetail, one launch failed due to Centaur upper stage issue]
-
A.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
B.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
C.
failureCauseOnFirstFlight
chosen
Indicates that an entity’s first flight resulted in a failure and specifies the cause of that failure.
-
D.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
E.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
- F. None of above.
Provenance (3 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd347d4481909e9094463011289d |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.