Triple
T24959438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terheijl |
E624564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place in Drenthe |
C14874
|
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: populated place in Drenthe Context triple: [Terheijl, instanceOf, populated place in Drenthe]
-
A.
populated place in the Netherlands
chosen
A populated place in the Netherlands is any geographically defined settlement area—such as a city, town, village, or hamlet—within Dutch territory where people live and engage in social, economic, and cultural activities.
-
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.
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.
-
D.
former municipality of the Netherlands
A former municipality of the Netherlands is an administrative region that once functioned as an independent local government unit but has since been merged, reorganized, or dissolved under Dutch municipal reforms.
-
E.
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.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 5:58 a.m.