Triple
T16811816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gjøvik Hockey |
E408631
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Gjøvik Hockey |
E408631
|
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 Hockey | Statement: [Gjøvik Hockey, hasNameInLanguage, Gjøvik Hockey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjøvik Hockey Context triple: [Gjøvik Hockey, hasNameInLanguage, Gjøvik Hockey]
-
A.
Gjøvik Hockey
chosen
Gjøvik Hockey is an ice hockey club based in Gjøvik, Norway, competing in the Norwegian league system.
-
B.
Storhamar Hockey
Storhamar Hockey is a professional ice hockey club from Hamar, Norway, known as one of the country’s most successful and storied teams.
-
C.
Sandnes HK
Sandnes HK is a Norwegian handball club based in the city of Sandnes.
-
D.
Lillehammer IK
Lillehammer IK is a Norwegian ice hockey club based in Lillehammer that competes in the country’s top leagues.
-
E.
FK Gjøvik-Lyn
FK Gjøvik-Lyn is a Norwegian football club based in the town of Gjøvik, competing in the national league system.
- 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.