Triple
T20836898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiklestad |
E512981
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Verdalsøra |
—
|
NE NERFINISHED |
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: Verdalsøra | Statement: [Stiklestad, near, Verdalsøra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Verdalsøra Context triple: [Stiklestad, near, Verdalsøra]
-
A.
Verdalsøra
chosen
Verdalsøra is a small town in Trøndelag county, Norway, known for its riverside setting and role as a local commercial and service hub.
-
B.
Sørreisa
Sørreisa is a small coastal municipality and village area in northern Norway known for its fjords and rural Arctic landscape.
-
C.
Vålebru
Vålebru is a village in Innlandet county, Norway, serving as the main local hub for services and administration in Ringebu municipality.
-
D.
Søråa
Søråa is a river located in the Namdalen district of Trøndelag county in central Norway.
-
E.
Stryn
Stryn is a municipality in Vestland county, Norway, known for its dramatic fjord and mountain landscapes, glaciers, and popular outdoor tourism activities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3280a1881909a86d1fe498aee50 |
completed | April 21, 2026, 12:22 a.m. |
Created at: April 16, 2026, 12:42 p.m.