Triple
T19967280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 03L/21R |
E479969
|
entity |
| Predicate | airportIATACode |
P418
|
FINISHED |
| Object | ESB |
—
|
NE NERFINISHED |
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: ESB | Statement: [Runway 03L/21R, airportIATACode, ESB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESB Context triple: [Runway 03L/21R, airportIATACode, ESB]
-
A.
ESB
ESB is the vehicle registration code used on license plates for the Neustadt an der Waldnaab district in Bavaria, Germany.
-
B.
ESB
ESB is a flagship premium bitter ale produced by Fuller’s Griffin Brewery in London, renowned for its rich, malty character and multiple award wins.
-
C.
ESB
chosen
ESB is the IATA airport code for Esenboğa International Airport, the main airport serving Ankara, Turkey.
-
D.
AquaLogic Enterprise Service Bus
AquaLogic Enterprise Service Bus is a middleware platform that enables integration and orchestration of services and applications within a service-oriented architecture (SOA).
-
E.
ES-IB
ES-IB is the ISO 3166-2 code representing the Spanish Balearic Islands province that includes Formentera.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
Created at: April 10, 2026, 1:54 p.m.