Triple
T8819828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Valley-Goose Bay Airport |
E209873
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | YYR |
E209872
|
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: YYR | Statement: [Happy Valley-Goose Bay Airport, IATA code, YYR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YYR Context triple: [Happy Valley-Goose Bay Airport, IATA code, YYR]
-
A.
YYR
chosen
YYR is the IATA airport code for Happy Valley-Goose Bay Airport, a regional air transport hub in Newfoundland and Labrador, Canada.
-
B.
CYYR
CYYR is the ICAO airport code for Happy Valley-Goose Bay Airport, a major airfield in Newfoundland and Labrador, Canada.
-
C.
YYT
YYT is the IATA airport code for St. John’s International Airport, the main air gateway to St. John’s, Newfoundland and Labrador, Canada.
-
D.
YRK
YRK is the National Rail station code for York railway station, a major historic rail hub in North Yorkshire, England.
-
E.
RYR
RYR is the ICAO airline designator used for Ryanair, a major Irish low-cost carrier operating extensive routes across Europe.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600fbbac8190ad36d93fff60a33f |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf89357b488190997f368079ef7e1e |
completed | April 3, 2026, 9:32 a.m. |
Created at: March 30, 2026, 6:46 p.m.