Triple
T15751380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyngseidet |
E381852
|
entity |
| Predicate | municipalFunction |
P3902
|
FINISHED |
| Object | local administration centre |
—
|
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: local administration centre | Statement: [Lyngseidet, municipalFunction, local administration centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalFunction Context triple: [Lyngseidet, municipalFunction, local administration centre]
-
A.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
B.
governmentalFunction
chosen
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
-
C.
municipalUse
Indicates that something is intended for, designated as, or used in connection with municipal or local government purposes.
-
D.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
E.
municipalIntegration
Indicates the incorporation or coordination of local governmental functions, services, or jurisdictions into a unified municipal framework.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.