Triple
T3145387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mjøsa |
E65750
|
entity |
| Predicate | locatedNearTown |
P3883
|
FINISHED |
| Object | Gjøvik |
E84018
|
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 | Statement: [Mjøsa, locatedNearTown, Gjøvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjøvik Context triple: [Mjøsa, locatedNearTown, Gjøvik]
-
A.
Gjøvik
chosen
Gjøvik is a town and municipality in Innlandet county, Norway, known for its location along Lake Mjøsa and its mix of industrial heritage and modern sports and cultural facilities.
-
B.
Lørenskog
Lørenskog is a suburban municipality in Viken county, Norway, located just east of Oslo and known for its residential areas and commercial centers.
-
C.
Drammen
Drammen is a city and municipality in southeastern Norway known for its riverside setting along the Drammenselva and its role as a regional commercial and transport hub.
-
D.
Bærum
Bærum is a wealthy suburban municipality just west of Oslo, Norway, known for its high standard of living and residential communities.
-
E.
Porsgrunn
Porsgrunn is an industrial and port city in Telemark county in southeastern Norway, known for its porcelain production and location along the Telemark Canal.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b276edde308190b26ac47ae1a79ce1 |
completed | March 12, 2026, 8:18 a.m. |
Created at: March 8, 2026, 3:05 p.m.