Triple
T2773602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morris Air |
E61515
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | YX |
E118837
|
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: YX | Statement: [Morris Air, IATAcode, YX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YX Context triple: [Morris Air, IATAcode, YX]
-
A.
YX
chosen
YX is the IATA airline designator used by Republic Airways, a major U.S. regional airline operating flights on behalf of larger carriers.
-
B.
YXU
YXU is the IATA airport code for London International Airport serving London, Ontario, Canada.
-
C.
XNYN
XNYN is the Market Identifier Code (MIC) assigned to the NYSE National stock exchange for identifying it in global securities trading and reporting systems.
-
D.
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.
-
E.
YMX
YMX is the IATA airport code for Montréal–Mirabel International Airport, a major cargo and aerospace hub located northwest of Montreal, Canada.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd7e29e08190921fd4ac9d0679ec |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc0553588819098d478b4aaa18478 |
completed | March 10, 2026, 6:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.