Triple

T3869608
Position Surface form Disambiguated ID Type / Status
Subject London City Airport E91949 entity
Predicate hasThreeLetterCode P2569 FINISHED
Object LCY E91949 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: LCY | Statement: [London City Airport, hasThreeLetterCode, LCY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LCY
Context triple: [London City Airport, hasThreeLetterCode, LCY]
  • A. LCY chosen
    LCY is the IATA airport code for London City Airport, a centrally located international airport serving London, United Kingdom.
  • B. Luyang
    Luyang is a historic name associated with the city of Hefei, the capital of Anhui Province in eastern China.
  • C. Cathay City
    Cathay City is Cathay Pacific’s purpose-built corporate headquarters complex located near Hong Kong International Airport, housing the airline’s main offices, training facilities, and support operations.
  • D. Lüshun
    Lüshun is a strategically important port city in northeastern China, historically known as Port Arthur and noted for its role in several major conflicts.
  • E. Yao Airport
    Yao Airport is a regional airport in Yao, Osaka Prefecture, Japan, primarily serving general aviation, flight training, and emergency services rather than major commercial airline traffic.
  • 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_69aed9645f348190a9868e7cef56ab7e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec533828819080f52dae15fdbecd completed March 9, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c83512c81908db2e442b7d2aca0 completed March 14, 2026, 8:29 a.m.
Created at: March 9, 2026, 3:20 p.m.