Triple
T16811779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FK Gjøvik-Lyn |
E408630
|
entity |
| Predicate | homeVenue |
P105
|
FINISHED |
| Object | Gjøvik Stadion |
E408629
|
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: Gjøvik Stadion | Statement: [FK Gjøvik-Lyn, homeVenue, Gjøvik Stadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjøvik Stadion Context triple: [FK Gjøvik-Lyn, homeVenue, Gjøvik Stadion]
-
A.
Gjøvik Stadium
chosen
Gjøvik Stadium is a sports arena in Gjøvik, Norway, primarily used for football and athletics events.
-
B.
Vålerenga Stadion
Vålerenga Stadion is a football stadium in Oslo, Norway, serving as the home ground of the Vålerenga Fotball club.
-
C.
Sarpsborg Stadion
Sarpsborg Stadion is a football stadium in Sarpsborg, Norway, primarily used as the home ground of the club Sarpsborg 08 FF.
-
D.
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.
-
E.
Bryne Stadion
Bryne Stadion is a football stadium in Bryne, Norway, primarily known as the home ground of the Norwegian club Bryne FK.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2d0793c81909d938ac174a6e63a |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b292a5888190812539b14eb77f34 |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:23 a.m.