Triple

T19446582
Position Surface form Disambiguated ID Type / Status
Subject Burbank Airport–South station E486492 entity
Predicate iataAirportServed P119918 FINISHED
Object BUR NE NERFINISHED

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: BUR | Statement: [Burbank Airport–South station, iataAirportServed, BUR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BUR
Context triple: [Burbank Airport–South station, iataAirportServed, BUR]
  • A. BUR chosen
    BUR is the three-letter IATA airport code for Hollywood Burbank Airport, a commercial airport serving the Los Angeles area in Southern California.
  • B. BUR
    BUR is the commonly used abbreviation for the Burnaby Lakers, a Canadian box lacrosse team based in Burnaby, British Columbia.
  • C. Br
    Br is the currency symbol used to denote the Ethiopian birr, the official monetary unit of Ethiopia.
  • D. BOR
    BOR is the commonly used abbreviation for the United States Bureau of Reclamation, a federal agency that manages water resources and hydroelectric power projects in the American West.
  • E. BOR
    BOR is the Polish Government Protection Bureau, a state security agency responsible for protecting top government officials and key state facilities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6338a22608190bb31a1690ca0dab6 completed April 20, 2026, 2:09 p.m.
Created at: April 10, 2026, 1:38 p.m.