Triple
T6894578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XiamenAir |
E159138
|
entity |
| Predicate | ICAOAirlineDesignator |
P26821
|
FINISHED |
| Object | CXA |
E159138
|
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: CXA | Statement: [XiamenAir, ICAOAirlineDesignator, CXA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CXA Context triple: [XiamenAir, ICAOAirlineDesignator, CXA]
-
A.
CXA
chosen
CXA is the ICAO airline designator used to identify XiamenAir in international aviation operations and communications.
-
B.
XCA
XCA (Cross-Community Access) is an IHE IT Infrastructure profile that enables the discovery and retrieval of patient health records across different healthcare communities or domains.
-
C.
CQX
CQX is the IATA airport code for Chatham Municipal Airport, a public airport serving Chatham, Massachusetts, in the United States.
-
D.
CBX
CBX is a pedestrian skybridge and terminal facility that connects San Diego directly to Tijuana International Airport, allowing ticketed passengers to cross the U.S.–Mexico border quickly and conveniently.
-
E.
CXP
CXP is the FAA location identifier for Carson City Airport in Carson City, Nevada.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d931da24819096b9b205f2c0ebb0 |
completed | March 27, 2026, 7:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748db2bd48190bb26f60c58ec8229 |
completed | March 28, 2026, 3:19 a.m. |
Created at: March 27, 2026, 2:24 p.m.