Triple
T2430056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1958 FIFA World Cup |
E52820
|
entity |
| Predicate | finalVenue |
P373
|
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: [1958 FIFA World Cup, finalVenue, Råsunda Stadium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Råsunda Stadium Context triple: [1958 FIFA World Cup, finalVenue, Råsunda Stadium]
-
A.
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.
-
B.
Ullevaal Stadion
Ullevaal Stadion is Norway’s national football stadium and a major sports and events arena located in Oslo.
-
C.
Soevereinstadion
Soevereinstadion is a football stadium in Lommel, Belgium, primarily used for hosting the home matches of Lommel SK.
-
D.
Ullevi Stadium
Ullevi Stadium is a major multi-purpose arena in Gothenburg, Sweden, known for hosting large football matches, athletics events, and concerts.
-
E.
Volksparkstadion
Volksparkstadion is a major football stadium in Hamburg, Germany, known for hosting top-level club and international matches, including games of the German national team.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc99fcd048190a85b95a9a8ae6d4d |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebf6634a48190af82eab6b9750323 |
completed | March 9, 2026, 12:39 p.m. |
Created at: March 6, 2026, 9:43 p.m.