Triple
T8002513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle Lake District Airport |
E186283
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | CAX |
E704193
|
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: CAX | Statement: [Carlisle Lake District Airport, pushpinLabel, CAX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CAX Context triple: [Carlisle Lake District Airport, pushpinLabel, CAX]
-
A.
CAX
chosen
CAX is the three-letter IATA airport code for Carlisle Lake District Airport in Cumbria, England.
-
B.
CXA
CXA is the ICAO airline designator used to identify XiamenAir in international aviation operations and communications.
-
C.
CXP
CXP is the FAA location identifier for Carson City Airport in Carson City, Nevada.
-
D.
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.
-
E.
CAB
CAB is the IEC Conformity Assessment Board, the body within the International Electrotechnical Commission that oversees and coordinates its global conformity assessment systems and activities.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf2918081909ee0afab11caed63 |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56910dd4819084ffe3350f15d95d |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:18 p.m.