Triple
T3897663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montréal–Mirabel International Airport |
E90407
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | YMX |
E90407
|
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: YMX | Statement: [Montréal–Mirabel International Airport, IATA code, YMX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YMX Context triple: [Montréal–Mirabel International Airport, IATA code, YMX]
-
A.
YMX
chosen
YMX is the IATA airport code for Montréal–Mirabel International Airport, a major cargo and aerospace hub located northwest of Montreal, Canada.
-
B.
MXY
MXY is the ICAO airline designator assigned to Breeze Airways, a U.S.-based low-cost carrier.
-
C.
YHM
YHM is the IATA airport code for John C. Munro Hamilton International Airport, a regional passenger and cargo airport serving the Hamilton, Ontario area in Canada.
-
D.
YX
YX is the IATA airline designator used by Republic Airways, a major U.S. regional airline operating flights on behalf of larger carriers.
-
E.
YXU
YXU is the IATA airport code for London International Airport serving London, Ontario, 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecd48b208190afaa62975805d087 |
completed | March 9, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51ca0f72c819084726f631a947f8c |
completed | March 14, 2026, 8:30 a.m. |
Created at: March 9, 2026, 3:21 p.m.