Triple
T5323062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London International Airport |
E121719
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | YXU |
E121719
|
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: YXU | Statement: [London International Airport, FAA LID, YXU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YXU Context triple: [London International Airport, FAA LID, YXU]
-
A.
YXU
chosen
YXU is the IATA airport code for London International Airport serving London, Ontario, Canada.
-
B.
YX
YX is the IATA airline designator used by Republic Airways, a major U.S. regional airline operating flights on behalf of larger carriers.
-
C.
XU
XU was a clandestine Norwegian intelligence organization that gathered and transmitted vital information to the Allies during the German occupation in World War II.
-
D.
YB
YB is the common abbreviation for BSC Young Boys, a professional football club based in Bern, Switzerland.
-
E.
YUC
YUC is the official vehicle registration code used on license plates for the Mexican state of Yucatán.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8577ba3881909a28cbf744648256 |
completed | March 20, 2026, 5:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf18a836988190b7baf3c24fea6f03 |
completed | March 21, 2026, 10:16 p.m. |
Created at: March 20, 2026, 1:59 p.m.