Triple
T19017101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Municipality of Wood Buffalo |
E465380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized municipality |
C27954
|
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: specialized municipality Context triple: [Regional Municipality of Wood Buffalo, instanceOf, specialized municipality]
-
A.
municipality
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.
-
B.
special-purpose district
A special-purpose district is a limited-purpose local government entity created to perform a specific public function or set of functions—such as water supply, transportation, or education—within a defined geographic area.
-
C.
municipality type
chosen
A municipality type is a classification that defines the legal, administrative, or functional category of a local government unit (such as city, town, or village) within a given jurisdiction.
-
D.
collective municipality
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
-
E.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.