Triple
T11640152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tromsø IL |
E276636
|
entity |
| Predicate | playsHomeMatchesAt |
P8186
|
FINISHED |
| Object | Alfheim Stadion |
E276637
|
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: Alfheim Stadion | Statement: [Tromsø IL, playsHomeMatchesAt, Alfheim Stadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alfheim Stadion Context triple: [Tromsø IL, playsHomeMatchesAt, Alfheim Stadion]
-
A.
Alfheim Stadion
chosen
Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
-
B.
Viking Stadion
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
C.
Aspmyra Stadion
Aspmyra Stadion is a football stadium in Bodø, Norway, best known as the home ground of FK Bodø/Glimt.
-
D.
Bosuilstadion
Bosuilstadion is a historic football stadium in Antwerp, Belgium, best known as the long-time home ground of Royal Antwerp F.C.
-
E.
Åråsen Stadion
Åråsen Stadion is a football stadium in Lillestrøm, Norway, best known as the main home ground of Lillestrøm SK and a prominent venue in Norwegian football.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef137087248190bb6c196bc94eb0f6 |
completed | April 27, 2026, 7:42 a.m. |
Created at: April 8, 2026, 9:39 p.m.