Triple
T3145660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenemangsstråket |
E65757
|
entity |
| Predicate | hasVenue |
P373
|
FINISHED |
| Object | Ullevi |
E66012
|
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: Ullevi | Statement: [Evenemangsstråket, hasVenue, Ullevi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ullevi Context triple: [Evenemangsstråket, hasVenue, Ullevi]
-
A.
Ullevi Stadium
chosen
Ullevi Stadium is a major multi-purpose arena in Gothenburg, Sweden, known for hosting large football matches, athletics events, and concerts.
-
B.
Oslo Spektrum
Oslo Spektrum is a large indoor arena in Oslo, Norway, primarily used for ice hockey, concerts, and major cultural and sporting events.
-
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.
Ullevaal Stadion
Ullevaal Stadion is Norway’s national football stadium and a major sports and events arena located in Oslo.
-
E.
ESPRIT Arena
ESPRIT Arena is a modern multi-purpose stadium in Düsseldorf, Germany, primarily used for football matches and large-scale events.
- 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.