Triple
T15744351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESB |
E381682
|
entity |
| Predicate | threeLetterCode |
P418
|
FINISHED |
| Object | ESB |
E381682
|
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: ESB | Statement: [ESB, threeLetterCode, ESB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESB Context triple: [ESB, threeLetterCode, 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
chosen
ESB is the IATA airport code for Esenboğa International Airport, the main airport serving Ankara, Turkey.
-
C.
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).
-
D.
ES-IB
ES-IB is the ISO 3166-2 code representing the Spanish Balearic Islands province that includes Formentera.
-
E.
ESW
ESW is the vehicle registration code for the German town and district of Eschwege in the state of Hesse.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0502c0c3c8190b8e512df307039c1 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8307824881909ba85e4c3da65d28 |
completed | May 9, 2026, 6:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.