Triple

T21639601
Position Surface form Disambiguated ID Type / Status
Subject CNXMN E534054 entity
Predicate codeComponent P86070 FINISHED
Object XMN (location code) 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: XMN (location code) | Statement: [CNXMN, codeComponent, XMN (location code)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: XMN (location code)
Context triple: [CNXMN, codeComponent, XMN (location code)]
  • A. XMN chosen
    XMN is the IATA airport code for Xiamen Gaoqi International Airport, the main air gateway serving Xiamen in Fujian Province, China.
  • B. CNXMN
    CNXMN is the UN/LOCODE identifier for the Port of Xiamen, a major seaport and shipping hub in southeastern China.
  • C. XiamenAir
    XiamenAir is a Chinese airline based in Xiamen that operates domestic and international flights across Asia and beyond.
  • D. XNM
    XNM is the IATA airport-style code assigned to Norwich railway station in Norwich, England, for use in integrated transport and ticketing systems.
  • E. BXM
    BXM is the railway station code for Brussels-South (Bruxelles-Midi / Brussel-Zuid), the main international and domestic rail hub in Brussels, Belgium.
  • 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_69e0c465ae7481908577b7209fdb2a77 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5390ba7481908f58230779e5b7bb completed April 27, 2026, 12:16 p.m.
Created at: April 16, 2026, 6:35 p.m.