Triple
T21052935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby Airport |
E518634
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | ESSV |
—
|
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: ESSV | Statement: [Visby Airport, ICAO code, ESSV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESSV Context triple: [Visby Airport, ICAO code, ESSV]
-
A.
ESSV
chosen
ESSV is the ICAO airport code for Visby Airport, the main airport serving the island of Gotland in Sweden.
-
B.
ESS
ESS is the commonly used abbreviation for the European Standardization System, the framework through which European standards are developed and harmonized.
-
C.
ESS
ESS is the commonly used abbreviation for Étoile Sportive du Sahel, a prominent multi-sport club based in Sousse, Tunisia, best known for its successful football team.
-
D.
ESVK
ESVK is a German ice hockey club based in Kaufbeuren, Bavaria, competing in the national league system.
-
E.
Esv
Esv is the official Dutch railway station code used to identify Eindhoven Strijp-S station in the Netherlands.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7cabe881909e6b258a14d501a6 |
completed | April 21, 2026, 4:30 a.m. |
Created at: April 16, 2026, 2:36 p.m.