Triple
T13127953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3 rocket |
E311891
|
entity |
| Predicate | allFlightsOutcome |
P108202
|
FINISHED |
| Object | failed to meet design goals |
—
|
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: failed to meet design goals | Statement: [A3 rocket, allFlightsOutcome, failed to meet design goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allFlightsOutcome Context triple: [A3 rocket, allFlightsOutcome, failed to meet design goals]
-
A.
offersFlights
Indicates that one entity provides or makes available flight services or routes to another entity or destination.
-
B.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
C.
numberOfFlights
Indicates the total count of flights associated with a given entity or within a specified context.
-
D.
allInternationalFlightsRouteVia
Indicates that every international flight to or from a given location must pass through a specified intermediate location or hub.
-
E.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:07 p.m.