Triple
T15302418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking Stadion |
E365820
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Viking Arena |
E365820
|
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: Viking Arena | Statement: [Viking Stadion, formerName, Viking Arena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viking Arena Context triple: [Viking Stadion, formerName, Viking Arena]
-
A.
Skagerak Arena
Skagerak Arena is a football stadium in Skien, Norway, best known as the home ground of the club Odds BK.
-
B.
Scandinavium arena
Scandinavium arena is a major indoor sports and entertainment venue in Gothenburg, Sweden, known for hosting ice hockey, concerts, and international events.
-
C.
Viking Stadion
chosen
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
D.
Läkerol Arena
Läkerol Arena is the former name of a multi-purpose indoor ice hockey arena in Gävle, Sweden, that has hosted home games for the Brynäs IF hockey team.
-
E.
Visma Arena
Visma Arena is a multi-purpose sports stadium in Växjö, Sweden, primarily used for football matches and home to local professional teams.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccd575c8190aa43262d3b73ef3c |
completed | April 16, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef86b8cc81909969098b1766f6b7 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:15 a.m.