Triple

T11564535
Position Surface form Disambiguated ID Type / Status
Subject Seoul–New York E274221 entity
Predicate IATACodeDestination P418 FINISHED
Object EWR E63393 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: EWR | Statement: [Seoul–New York, IATACodeDestination, EWR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EWR
Context triple: [Seoul–New York, IATACodeDestination, EWR]
  • A. EWR chosen
    EWR is the three-letter IATA airport code for Newark Liberty International Airport, a major air travel hub serving the New York City metropolitan area.
  • B. EWE
    EWE is the National Rail station code for Ewell West railway station in Surrey, England.
  • C. WRR
    WRR is the commonly used abbreviation for the Western Recruiting Region, a U.S. military administrative area responsible for managing recruitment activities across the western United States.
  • D. RWR
    RWR is the abbreviation for the Royal Winnipeg Rifles, an infantry regiment of the Canadian Army Reserve based in Winnipeg, Manitoba.
  • E. EYW
    EYW is the IATA airport code for Key West International Airport, a small commercial airport serving Key West in the Florida Keys, USA.
  • 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d88dd321f88190a57ecaf079fbbc3f completed April 10, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6e8b1a67481909a05105728acc358 completed April 21, 2026, 3:02 a.m.
Created at: April 8, 2026, 9:37 p.m.