Triple

T2332027
Position Surface form Disambiguated ID Type / Status
Subject United Airlines Flight 93 E44223 entity
Predicate crashLongitudeApprox P1282 FINISHED
Object -78.905 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: -78.905 | Statement: [United Airlines Flight 93, crashLongitudeApprox, -78.905]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crashLongitudeApprox
Context triple: [United Airlines Flight 93, crashLongitudeApprox, -78.905]
  • A. coordinateLongitude chosen
    Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
  • B. coordinateLatitude
    Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
  • C. colongitude
    Indicates the angular distance of a point (typically on a rotating body) measured westward from a defined prime meridian, often used to specify its position relative to the body’s rotation or illumination.
  • D. hasApproximateCoordinates
    Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
  • E. crashCountry
    Indicates that an aviation crash event occurred within the territory or jurisdiction of a specified country.
  • 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_69a889132b488190bbb43ad4780ddd92 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abcc30c5e881908c5d526d7e7491d0 completed March 7, 2026, 6:56 a.m.
PD Predicate disambiguation batch_69abc5926d048190a535e3f23d41de2a completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:51 p.m.