Triple
T28989330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reykjavíkurborg |
E734778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local administrative entity |
C39
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: local administrative entity Context triple: [Reykjavíkurborg, instanceOf, local administrative entity]
-
A.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
B.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
C.
administrative community
An administrative community is a group of individuals and organizations connected through shared governance structures, procedures, and responsibilities for managing and implementing policies or services within a defined domain.
-
D.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
-
E.
municipality
chosen
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- F. None of above.
Provenance (1 batch)
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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:16 a.m.