Triple
T20999360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levanger |
E517242
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Verdal |
—
|
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: Verdal | Statement: [Levanger, locatedNear, Verdal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Verdal Context triple: [Levanger, locatedNear, Verdal]
-
A.
Verdal
chosen
Verdal is a municipality in central Norway known for its agricultural landscape, industrial activity, and the historic battlefield of Stiklestad.
-
B.
Vaksdal
Vaksdal is a village in Vestland county, Norway, situated along the Veafjorden and known for its historic textile industry and railway connections.
-
C.
Nissedal
Nissedal is a rural municipality in Vestfold og Telemark county, Norway, known for its forests, lakes, and outdoor recreation opportunities.
-
D.
Vedvik
Vedvik is a small coastal village in the former Vågsøy municipality in Vestland county, western Norway.
-
E.
Eidsvåg
Eidsvåg is a village in Møre og Romsdal county, Norway, known for its fjord-side location and role as a local service and industrial hub.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc2395108190871e173354e4ef6f |
completed | April 21, 2026, 4:25 a.m. |
Created at: April 16, 2026, 1:51 p.m.