Triple
T38084705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinets of Hendrikus Colijn |
E950945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical government entity |
C1003
|
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: historical government entity Context triple: [Cabinets of Hendrikus Colijn, instanceOf, historical government entity]
-
A.
ancient political entity
An ancient political entity is a historically situated, organized community or state that exercised authority, governance, and control over a defined territory and population in antiquity.
-
B.
former political institution
chosen
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
C.
government of a former country
A government of a former country is the political authority and administrative system that once exercised sovereign control over a now-dissolved, absorbed, or reconstituted state.
-
D.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.