Triple

T5241267
Position Surface form Disambiguated ID Type / Status
Subject Terminal 2 E118345 entity
Predicate connectedTo P37 FINISHED
Object Terminal 5 unclear NED1 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: Terminal 5 | Statement: [Terminal 2, connectedTo, Terminal 5]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Terminal 5
Context triple: [Terminal 2, connectedTo, Terminal 5]
  • A. Terminal 5
    Terminal 5 is a major passenger terminal at John F. Kennedy International Airport in New York City, known for serving as the primary hub for JetBlue Airways.
  • B. Terminal 5
    Terminal 5 is one of the passenger terminals at José Martí International Airport in Havana, Cuba, serving specific airlines and routes.
  • C. Terminal 5
    Terminal 5 is a major, modern passenger terminal at London Heathrow Airport primarily serving British Airways and Iberia flights.
  • D. Terminal 5
    Terminal 5 is a dedicated passenger terminal at Rome’s Leonardo da Vinci–Fiumicino Airport, primarily used for certain international and long-haul flights.
  • E. Terminal 5
    Terminal 5 is a passenger terminal facility at Mehrabad International Airport in Tehran, Iran.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69bd4467db0881909b3b0982df32cc8f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b2c50508190b84bab216c30cbfe completed March 20, 2026, 4:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf06b8a0e881909d6037fb8fca1236 completed March 21, 2026, 8:59 p.m.
Created at: March 20, 2026, 1:49 p.m.