Triple
T2317200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Groningen |
E51092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constituent territory of the Seventeen Provinces |
C3295
|
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: constituent territory of the Seventeen Provinces Context triple: [Lordship of Groningen, instanceOf, constituent territory of the Seventeen Provinces]
-
A.
Dutch colonial province
A Dutch colonial province is an administrative region established and governed by the Netherlands in its overseas territories, typically managed by appointed colonial officials under Dutch law and economic interests.
-
B.
vassal state
chosen
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
C.
Dutch colonial territory
A Dutch colonial territory is a region outside Europe that was politically and economically controlled and administered by the Netherlands as part of its overseas empire.
-
D.
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.
-
E.
former Dutch colony
A former Dutch colony is a territory that was once governed, administered, or significantly controlled by the Netherlands as part of its overseas colonial empire, but has since gained independence or been transferred to another sovereignty.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:49 p.m.