Triple
T6786201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty of Amsterdam |
E155809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency of the Dutch Republic |
C14100
|
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: government agency of the Dutch Republic Context triple: [Admiralty of Amsterdam, instanceOf, government agency of the Dutch Republic]
-
A.
government body of the Kingdom of the Netherlands
A government body of the Kingdom of the Netherlands is an official public institution or authority, established by law, that exercises administrative, legislative, or judicial powers on behalf of the Dutch state or its constituent parts.
-
B.
Dutch public body
chosen
A Dutch public body is an organization established by or under Dutch public law, entrusted with performing public tasks or exercising public authority under government oversight.
-
C.
organ of the Dutch West India Company
An organ of the Dutch West India Company is any official governing, administrative, or executive body (such as the directors, chambers, or councils) through which the Company exercised its legal powers and conducted its affairs.
-
D.
Dutch colonial figure
A Dutch colonial figure is an individual from the Netherlands who played a significant role in the administration, expansion, or cultural impact of Dutch overseas territories during the colonial period.
-
E.
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.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.