Triple

T14948308
Position Surface form Disambiguated ID Type / Status
Subject New Chitose Airport E372724 entity
Predicate IATA code P2569 FINISHED
Object CTS E372724 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: CTS | Statement: [New Chitose Airport, IATA code, CTS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CTS
Context triple: [New Chitose Airport, IATA code, CTS]
  • A. CTS
    CTS is the acronym for the Council for Trade in Services, a World Trade Organization body responsible for overseeing the implementation and functioning of global rules on trade in services.
  • B. CTS
    CTS is the public transport operator responsible for running Strasbourg’s tram and bus network in France.
  • C. CTS chosen
    CTS is the IATA airport code for New Chitose Airport, the main international gateway serving Sapporo and the Hokkaido region of Japan.
  • D. CCT
    CCT is the station code for Kakinada Town railway station, a key rail hub in the city of Kakinada in Andhra Pradesh, India.
  • E. CTI
    CTI is the French national accreditation body responsible for evaluating and authorizing engineering degree programs.
  • 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_69d85cca979481908747d2a81eba1cea completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded68e35c481908e47cd68441c5115 completed April 15, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e986dfc8190a5cf363dabe6bdef completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 2:39 a.m.