Triple
T7061383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury Airport |
E164222
|
entity |
| Predicate | code |
P1537
|
FINISHED |
| Object | YMAY |
E638912
|
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: YMAY | Statement: [Albury Airport, code, YMAY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YMAY Context triple: [Albury Airport, code, YMAY]
-
A.
YMAY
chosen
YMAY is the ICAO airport code for Albury Airport, a regional airport serving the city of Albury in New South Wales, Australia.
-
B.
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.
-
C.
CYAM
CYAM is the ICAO airport code for Sault Ste. Marie Airport in Ontario, Canada.
-
D.
YMX
YMX is the IATA airport code for Montréal–Mirabel International Airport, a major cargo and aerospace hub located northwest of Montreal, Canada.
-
E.
Amay
Amay is a municipality in the Walloon Region of Belgium, located in the province of Liège along the Meuse River.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e45b7488819094d2dd337731dab9 |
completed | March 27, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7944b4a60819089e565cb895c432f |
completed | March 28, 2026, 8:41 a.m. |
Created at: March 27, 2026, 2:38 p.m.