Triple
T23470240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora 7 |
E569205
|
entity |
| Predicate | landingDistanceFromPlanned |
P152396
|
FINISHED |
| Object | about 400 kilometers off course |
—
|
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: about 400 kilometers off course | Statement: [Aurora 7, landingDistanceFromPlanned, about 400 kilometers off course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingDistanceFromPlanned Context triple: [Aurora 7, landingDistanceFromPlanned, about 400 kilometers off course]
-
A.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
B.
distanceOfTouchdown
Indicates the measured distance from the line of scrimmage to the point where a touchdown is scored.
-
C.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
D.
proximityToRunway
Indicates how close an object or location is to a runway, typically in terms of distance or relative position.
-
E.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6ff8dc0819086961b1f07030d9c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.