Triple

T4866038
Position Surface form Disambiguated ID Type / Status
Subject Charing Cross Underground station E108771 entity
Predicate stationCode P1289 FINISHED
Object CHX E212176 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: CHX | Statement: [Charing Cross Underground station, stationCode, CHX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CHX
Context triple: [Charing Cross Underground station, stationCode, CHX]
  • A. CHX chosen
    CHX is the National Rail station code for London Charing Cross, a major central London railway terminus and transport hub.
  • B. XCH
    XCH is the IATA airport code for Christmas Island’s main international airport in the Indian Ocean.
  • C. CHQ
    CHQ is the ICAO airline designator assigned to Chautauqua Airlines, a former U.S. regional carrier that operated feeder services for major airlines.
  • D. CHS
    CHS is the abbreviation for the Committee on Hemispheric Security, a body within the Organization of American States focused on security issues in the Western Hemisphere.
  • E. CHS
    CHS is the three-letter IATA airport code for Charleston International Airport, the primary commercial airport serving the Charleston, South Carolina area.
  • 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_69bd440b965081908b0557721cae6338 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d7a42f88190bb1ef7261bcbc2a8 completed March 20, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67e0d88881909e378e919daab4e6 completed March 21, 2026, 9:41 a.m.
Created at: March 20, 2026, 1:26 p.m.