Triple
T17610265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langley Aerodrome |
E428947
|
entity |
| Predicate | primaryFailureCause |
P77548
|
FINISHED |
| Object | structural and launch system failures |
—
|
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: structural and launch system failures | Statement: [Langley Aerodrome, primaryFailureCause, structural and launch system failures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFailureCause Context triple: [Langley Aerodrome, primaryFailureCause, structural and launch system failures]
-
A.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
D.
primaryIssue
Indicates that the related item is the main or most important issue among a set of issues.
-
E.
failureCauseOnFirstFlight
Indicates that an entity’s first flight resulted in a failure and specifies the cause of that failure.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2d294881908380b2ab0b4d2503 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.