Triple

T16169897
Position Surface form Disambiguated ID Type / Status
Subject Orlando Executive Airport E392406 entity
Predicate FAA LID P420 FINISHED
Object ORL E394927 NE 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: ORL | Statement: [Orlando Executive Airport, FAA LID, ORL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ORL
Context triple: [Orlando Executive Airport, FAA LID, ORL]
  • A. ORL
    ORL is the standard three-letter abbreviation used for the NBA team Orlando Magic.
  • B. ORL chosen
    ORL is the FAA location identifier for Orlando Executive Airport, a public airport serving general aviation near downtown Orlando, Florida.
  • C. the Nose
    The Nose is the absurd, anthropomorphized facial feature that becomes an independent character in Nikolai Gogol’s satirical short story of the same name.
  • D. Lefort
    Lefort is a surname most notably associated with Franz Lefort, a 17th-century Genevan-born military officer and close advisor to Russian Tsar Peter the Great.
  • E. Ornea
    Ornea is a minor figure in Greek mythology known primarily as one of the many children of the river god Asopus.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f1d32208190942e4e499a80c18c completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21eb6de30819083af54b50ae5ae51 completed April 17, 2026, 11:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69fffefc3e088190975ecbdaeba7ee84 completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 5:02 a.m.