Triple
T1148408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor International Airport |
E23619
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | YQG |
E131552
|
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: YQG | Statement: [Windsor International Airport, alternativeName, YQG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YQG Context triple: [Windsor International Airport, alternativeName, YQG]
-
A.
YQG
chosen
YQG is the IATA airport code for Windsor International Airport, a commercial airport serving Windsor, Ontario, Canada and the surrounding region.
-
B.
YQT
YQT is the IATA airport code for Thunder Bay International Airport, a regional air transport hub in Thunder Bay, Ontario, Canada.
-
C.
YKF
YKF is the IATA airport code for Region of Waterloo International Airport serving the Kitchener–Waterloo area in Ontario, 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc7190308190ab104480ed208b22 |
completed | March 1, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac6f139a008190a20f38330364dd2b |
completed | March 7, 2026, 6:31 p.m. |
Created at: March 1, 2026, 7:44 p.m.