Triple
T35715888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geschiedenis des Vaderlands |
E1032003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of the Netherlands |
C65991
|
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: history of the Netherlands Context triple: [Geschiedenis des Vaderlands, instanceOf, history of the Netherlands]
-
A.
year in Dutch history
A year in Dutch history represents a specific 12-month period marked by political, social, economic, and cultural events that influenced the development of the Netherlands.
-
B.
historisch wereldrijk
Een historisch wereldrijk is een grootschalige, vaak multinationale staatkundige eenheid uit het verleden die over uitgestrekte gebieden en diverse volkeren heerste en langdurige politieke, culturele en economische invloed uitoefende.
-
C.
Dutch tradition
Dutch tradition encompasses the customs, festivals, values, and everyday practices that have developed in the Netherlands over centuries, reflecting its history, regional diversity, and cultural identity.
-
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.
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.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.