Triple
T15302446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking FK |
E365821
|
entity |
| Predicate | homeStadium |
P890
|
FINISHED |
| Object | Viking Stadion |
E365820
|
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: Viking Stadion | Statement: [Viking FK, homeStadium, Viking Stadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viking Stadion Context triple: [Viking FK, homeStadium, Viking Stadion]
-
A.
Viking Stadion
chosen
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
B.
Alfheim Stadion
Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
-
C.
Nadderud Stadion
Nadderud Stadion is a football stadium in Bærum, Norway, best known as the long-time home ground of Norwegian club Stabæk Fotball.
-
D.
Daknamstadion
Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
-
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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccd575c8190aa43262d3b73ef3c |
completed | April 16, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef89bb46481908f27fa98eb6ac5c3 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:15 a.m.