Triple
T13800286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisebergshallen |
E331620
|
entity |
| Predicate | locatedNear |
P294
|
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: [Lisebergshallen, locatedNear, Ullevi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ullevi Context triple: [Lisebergshallen, locatedNear, 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.
Skagerak Arena
Skagerak Arena is a football stadium in Skien, Norway, best known as the home ground of the club Odds BK.
-
D.
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.
-
E.
Daknamstadion
Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1b8689c8190b3ef7416000ef89e |
completed | May 6, 2026, 8:16 p.m. |
Created at: April 9, 2026, 10:11 p.m.