Triple
T34126773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Drenthe |
E875302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department of the Batavian Republic |
C3576
|
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: department of the Batavian Republic Context triple: [Department of Drenthe, instanceOf, department of the Batavian Republic]
-
A.
department of the Duchy of Warsaw
A department of the Duchy of Warsaw was an administrative division, similar to a province, established within the Napoleonic client state between 1807 and 1815 to organize local governance, justice, and taxation.
-
B.
department of France
chosen
A department of France is an administrative territorial division within the country, situated between the region and commune levels, responsible for local governance, public services, and implementation of national policies.
-
C.
organ of the French First Republic
An organ of the French First Republic is an official governmental body or institution established between 1792 and 1804 to exercise legislative, executive, or judicial authority within the republican state.
-
D.
Count of Holland
The Count of Holland was the medieval and early modern noble title held by the ruler of the County of Holland, a significant feudal territory in what is now the western Netherlands.
-
E.
King of Holland
The King of Holland is the hereditary head of state of the Netherlands, representing national unity, performing constitutional and ceremonial duties, and serving as a symbolic figure domestically and internationally.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.