Triple
T17800105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illawarra Regional Airport |
E444400
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | WOL |
E1117900
|
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: WOL | Statement: [Illawarra Regional Airport, hasIATAcode, WOL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WOL Context triple: [Illawarra Regional Airport, hasIATAcode, WOL]
-
A.
WOL
WOL is a German vehicle registration code formerly used for the town of Wolfach in the Ortenaukreis district of Baden-Württemberg.
-
B.
WOL
chosen
WOL is the station code for Wollongong railway station in New South Wales, Australia.
-
C.
wol
"wol" is the ISO 639-3 language code for Wolof, a major Atlantic language spoken primarily in Senegal, The Gambia, and Mauritania.
-
D.
WOFL
WOFL is a Fox-affiliated television station serving the Orlando, Florida media market.
-
E.
WPE
WPE is a major expressway in the Indian state of Haryana that forms part of a ring road system around Delhi to divert heavy traffic away from the city.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fe19dc8190b7e9dc96f39e0861 |
completed | April 19, 2026, 7:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a02f84095f48190985b20bc8f049e5b |
completed | May 12, 2026, 9:52 a.m. |
Created at: April 10, 2026, 10:13 a.m.