Triple
T22244390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niedersachsenstadion |
E549804
|
entity |
| Predicate | hasFormerName |
P65
|
FINISHED |
| Object | HDI-Arena |
—
|
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: HDI-Arena | Statement: [Niedersachsenstadion, hasFormerName, HDI-Arena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HDI-Arena Context triple: [Niedersachsenstadion, hasFormerName, HDI-Arena]
-
A.
HDI-Arena
chosen
HDI-Arena is a football stadium in Hanover, Germany, best known as the home ground of the Bundesliga club Hannover 96.
-
B.
Sparkassen-Arena
Sparkassen-Arena is a major indoor sports and events arena in Kiel, Germany, best known as the longtime home venue of the handball club THW Kiel.
-
C.
SchücoArena
SchücoArena is a football stadium in Bielefeld, Germany, best known as the home ground of the club Arminia Bielefeld.
-
D.
Preussag Arena
Preussag Arena is a large multi-purpose indoor arena in Hanover, Germany, primarily used for concerts and sporting events.
-
E.
Voith-Arena
Voith-Arena is a football stadium in Heidenheim, Germany, primarily known as the venue for 1. FC Heidenheim’s home matches.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132170e5081909b9dbb204abf2a45 |
completed | April 28, 2026, 10:17 p.m. |
Created at: April 16, 2026, 8:38 p.m.