Triple
T10428208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nedre Eiker |
E245840
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Mjøndalen |
E433548
|
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: Mjøndalen | Statement: [Nedre Eiker, containsSettlement, Mjøndalen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mjøndalen Context triple: [Nedre Eiker, containsSettlement, Mjøndalen]
-
A.
Mjøndalen
chosen
Mjøndalen is a town in Viken county, Norway, known historically for its industry and for its football club Mjøndalen IF.
-
B.
Vålerenga
Vålerenga is a neighborhood in Oslo, Norway, known for its working-class roots and strong association with the local football club Vålerenga Fotball.
-
C.
Lillestrøm
Lillestrøm is a Norwegian town and former municipality in the Greater Oslo Region, known as a regional commercial center and transport hub.
-
D.
Tromsø IL
Tromsø IL is a Norwegian professional football club based in the city of Tromsø, known for competing in the country’s top divisions and for being one of the world’s northernmost elite clubs.
-
E.
Tippeligaen
Tippeligaen was the former sponsored name of Norway’s top-tier professional football league, now known as Eliteserien.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4a7dcc81909a830e08656a1c0c |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d89f8a5b00819080c303bb0fc82f5a |
completed | April 10, 2026, 6:58 a.m. |
Created at: April 6, 2026, 12:13 p.m.