Triple
T8002732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bærum |
E186288
|
entity |
| Predicate | hasInstitution |
P186
|
FINISHED |
| Object | Nadderud Stadium |
E570974
|
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: Nadderud Stadium | Statement: [Bærum, hasInstitution, Nadderud Stadium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nadderud Stadium Context triple: [Bærum, hasInstitution, Nadderud Stadium]
-
A.
Nadderud Stadion
chosen
Nadderud Stadion is a football stadium in Bærum, Norway, best known as the long-time home ground of Norwegian club Stabæk Fotball.
-
B.
Gjøvik Stadium
Gjøvik Stadium is a sports arena in Gjøvik, Norway, primarily used for football and athletics events.
-
C.
Å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.
-
D.
Vålerenga Stadion
Vålerenga Stadion is a football stadium in Oslo, Norway, serving as the home ground of the Vålerenga Fotball club.
-
E.
Lerkendal Stadion
Lerkendal Stadion is a major football stadium in Trondheim, Norway, best known as the home ground of top Norwegian club Rosenborg BK.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf2918081909ee0afab11caed63 |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63bf5efc8190aa5cdc6707adbf71 |
completed | April 1, 2026, 12:15 a.m. |
Created at: March 30, 2026, 5:18 p.m.