Triple
T4740279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Netherlands |
E105221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of the Netherlands |
C16289
|
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: region of the Netherlands Context triple: [Eastern Netherlands, instanceOf, region of the Netherlands]
-
A.
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.
-
B.
region of Belgium
A region of Belgium is a first-level administrative division with its own government and competencies, such as Flanders, Wallonia, or the Brussels-Capital Region.
-
C.
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.
-
D.
country of the Kingdom of the Netherlands
A country of the Kingdom of the Netherlands is a constituent state within the Kingdom’s federal-like constitutional structure, possessing its own government and autonomy in internal affairs while sharing the monarch, foreign policy, and defense with the other countries.
-
E.
populated place in the Netherlands
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.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:19 p.m.