Triple
T3216135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-90 hill |
E67398
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Innlandet |
E65742
|
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: Innlandet | Statement: [K-90 hill, region, Innlandet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Innlandet Context triple: [K-90 hill, region, Innlandet]
-
A.
Innlandet
chosen
Innlandet is a county in eastern Norway known for its inland landscapes, including mountains, forests, and important winter sports venues.
-
B.
Hadeland
Hadeland is a traditional rural district in southeastern Norway known for its agricultural landscape, historic churches, and the Hadeland Glassverk glassworks.
-
C.
Numedal
Numedal is a valley in southeastern Norway known for its traditional wooden architecture, medieval stave churches, and scenic river landscape.
-
D.
Hallingdal
Hallingdal is a major valley and traditional district in southeastern Norway, known for its river, ski resorts, and rich folk culture.
-
E.
Trøndelag
Trøndelag is a central region of Norway known for its historic city of Trondheim, coastal landscapes, and strong cultural traditions.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2771204e0819086ae2838a368589a |
completed | March 12, 2026, 8:19 a.m. |
Created at: March 8, 2026, 3:07 p.m.