Triple
T3145606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frölunda HC |
E65756
|
entity |
| Predicate | homeArena |
P373
|
FINISHED |
| Object | Scandinavium |
E10970
|
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: Scandinavium | Statement: [Frölunda HC, homeArena, Scandinavium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Scandinavium Context triple: [Frölunda HC, homeArena, Scandinavium]
-
A.
Scandinavium
chosen
Scandinavium is a major indoor arena in Gothenburg, Sweden, best known for hosting top-level ice hockey, concerts, and international sporting events.
-
B.
Skaland
Skaland is a small coastal village on the island of Senja in northern Norway, known for its scenic fjord landscape and proximity to rugged mountains.
-
C.
Nord
Nord is a department in northern France known for its industrial heritage, dense population, and proximity to Belgium.
-
D.
Solbo
Solbo is a locality within Botkyrka Municipality in Stockholm County, Sweden.
-
E.
Svealand
Svealand is the central region of Sweden, historically significant as the country's core area and home to the capital city, Stockholm.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b224f18e80819083be53c556d56947 |
completed | March 12, 2026, 2:29 a.m. |
Created at: March 8, 2026, 3:05 p.m.