Triple
T22641647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verdalsøra |
E558842
|
entity |
| Predicate | municipalityWebsite |
P30293
|
FINISHED |
| Object | https://www.verdal.kommune.no/ |
—
|
LITERAL 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: https://www.verdal.kommune.no/ | Statement: [Verdalsøra, municipalityWebsite, https://www.verdal.kommune.no/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityWebsite Context triple: [Verdalsøra, municipalityWebsite, https://www.verdal.kommune.no/]
-
A.
hasLocalGovernmentWebsite
chosen
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
B.
governingBodyWebsite
Indicates the official website associated with the governing body responsible for an entity.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
E.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
- F. None of above.
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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703489a48190bd97a7eb7a571b64 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.