Triple
T2705905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariane 5 ECA |
E59340
|
entity |
| Predicate | firstFlightOutcome |
P42104
|
FINISHED |
| Object | failure |
—
|
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: failure | Statement: [Ariane 5 ECA, firstFlightOutcome, failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightOutcome Context triple: [Ariane 5 ECA, firstFlightOutcome, failure]
-
A.
firstFlightService
Indicates that an entity operates or provides service on the earliest scheduled flight in a given context or route.
-
B.
failureCauseOnFirstFlight
Indicates that an entity’s first flight resulted in a failure and specifies the cause of that failure.
-
C.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
-
D.
firstFlightPayload
Indicates that the object is the payload carried on an entity’s first flight.
-
E.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda559a908190ad5d92c11a398a03 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.