Triple
T6332165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hope Airport |
E142405
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | YHM |
E121254
|
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: YHM | Statement: [Mount Hope Airport, hasIATACode, YHM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YHM Context triple: [Mount Hope Airport, hasIATACode, YHM]
-
A.
YHM
chosen
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.
-
B.
CYHM
CYHM is the ICAO airport code for John C. Munro Hamilton International Airport in Hamilton, Ontario, Canada.
-
C.
HYM
HYM is the National Rail station code for Haymarket railway station in Edinburgh, Scotland.
-
D.
YMHB
YMHB is the ICAO airport code assigned to Hobart Airport, the main airport serving Hobart in Tasmania, Australia.
-
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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651634b08190b54860ba0a70f5c4 |
completed | March 22, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6041f713c8190b27ba54181049377 |
completed | March 27, 2026, 4:14 a.m. |
Created at: March 22, 2026, 4:30 p.m.