Triple
T3770394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Office (Kabinet van de Koning) |
E82782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch public body |
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: Dutch public body Context triple: [King’s Office (Kabinet van de Koning), instanceOf, Dutch public body]
-
A.
Belgian federal government
The Belgian federal government is the central governing authority of Belgium, responsible for national policy areas such as defense, justice, social security, and federal finance, operating within a complex federal system that shares powers with regional and community governments.
-
B.
Dutch company
A Dutch company is a business entity established under the laws of the Netherlands, typically registered with the Dutch Chamber of Commerce and subject to Dutch corporate, tax, and regulatory frameworks.
-
C.
Dutch state occasion
A Dutch state occasion is a formal, ceremonial event organized or hosted by the Kingdom of the Netherlands to mark significant national, diplomatic, or royal milestones.
-
D.
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.
-
E.
federal entity of Belgium
A federal entity of Belgium is one of the constitutionally recognized components of the Belgian state—either a region or a community—endowed with its own government, parliament, and specific legislative and administrative powers.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.