Triple
T13262695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenvik Municipality |
E315837
|
entity |
| Predicate | hadMunicipalNumber |
P83825
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Lenvik Municipality, hadMunicipalNumber, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMunicipalNumber Context triple: [Lenvik Municipality, hadMunicipalNumber, 1920]
-
A.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
B.
formerMunicipalityNumber
chosen
Indicates that an entity was previously assigned a specific official municipality identification number before administrative or territorial changes.
-
C.
hasMunicipalPart
Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
-
D.
hasMunicipalityCode
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
E.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.