Triple
T20643133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannover Airport |
E507280
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | EDDV |
—
|
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: EDDV | Statement: [Hannover Airport, ICAO code, EDDV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EDDV Context triple: [Hannover Airport, ICAO code, EDDV]
-
A.
EDDV
chosen
EDDV is the ICAO airport code for Hannover Airport, a major international airport serving the city of Hanover in northern Germany.
-
B.
EDDP
EDDP is the ICAO airport code for Leipzig/Halle Airport, a major international cargo and passenger airport in eastern Germany.
-
C.
EDD
EDD is the California state agency responsible for administering unemployment insurance, disability insurance, paid family leave, and various workforce and labor market programs.
-
D.
EDD
EDD is the National Rail station code for Eddington railway station in the United Kingdom.
-
E.
EDD
EDD was a Eurosceptic political group in the European Parliament that brought together parties critical of deeper European integration.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af1c51f48190abba54a5aace9fc8 |
completed | April 20, 2026, 10:56 p.m. |
Created at: April 16, 2026, 11:43 a.m.