Triple
T4882921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Råsunda |
E109371
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Råsunda Stadium |
E109371
|
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: Råsunda Stadium | Statement: [Råsunda, knownFor, Råsunda Stadium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Råsunda Stadium Context triple: [Råsunda, knownFor, Råsunda Stadium]
-
A.
Stockholm Olympic Stadium
Stockholm Olympic Stadium is a historic multi-purpose arena in Stockholm, Sweden, best known for hosting the 1912 Summer Olympics and for its distinctive brick architecture.
-
B.
Råsunda
chosen
Råsunda is a district in Solna, Sweden, historically known for hosting the former Råsunda Stadium, once the national football arena.
-
C.
Alfheim Stadion
Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
-
D.
Viking Stadion
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
E.
Ullevaal Stadion
Ullevaal Stadion is Norway’s national football stadium and a major sports and events arena located in Oslo.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddfff0c81908fb148a6f6508334 |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fb8e8f081908cee75f80494dd7d |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:27 p.m.