Triple
T5453027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Grave |
E122412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former municipality of the Netherlands |
C18102
|
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: former municipality of the Netherlands Context triple: [municipality of Grave, instanceOf, former municipality of the Netherlands]
-
A.
special municipality of the Netherlands
A special municipality of the Netherlands is a public body in the Caribbean that is directly administered by the Dutch central government but is not part of any Dutch province.
-
B.
town in the Netherlands
A town in the Netherlands is a moderately sized, locally governed urban settlement characterized by residential neighborhoods, commercial areas, public services, and cultural or historical features within Dutch territory.
-
C.
province of the Netherlands
A province of the Netherlands is a primary administrative division of the country, governed by its own provincial authorities and responsible for regional planning, infrastructure, and certain public services within its territory.
-
D.
municipality of Belgium
A municipality of Belgium is the smallest administrative division in the country, governed by a local council and mayor, responsible for providing public services and local regulations within its defined territory.
-
E.
region of the Netherlands
A region of the Netherlands is a geographically and culturally defined area within the country, often used for administrative, historical, or socio-economic purposes.
- F. None of above. chosen
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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:08 p.m.