Triple
T16366977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Commissioner in the province of Drenthe |
E397461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representative of the Dutch monarch |
C37357
|
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: representative of the Dutch monarch Context triple: [Queen's Commissioner in the province of Drenthe, instanceOf, representative of the Dutch monarch]
-
A.
representative of the British monarch
An official individual appointed to act on behalf of the British monarch, exercising certain royal powers and duties within a defined jurisdiction or context.
-
B.
regent of the Netherlands
A regent of the Netherlands is an individual appointed to temporarily exercise the constitutional powers and duties of the Dutch monarch when the monarch is unable to reign or the throne is vacant.
-
C.
Dutch royal
A Dutch royal is a member of the Netherlands' reigning House of Orange-Nassau, holding constitutional, ceremonial, and representative roles within the Dutch monarchy.
-
D.
Dutch regent
A Dutch regent was a member of the wealthy urban patrician elite who governed cities and provinces in the Dutch Republic, often holding multiple civic offices and exerting significant political and economic influence.
-
E.
Prince Consort of the Netherlands
The Prince Consort of the Netherlands is the husband of the reigning Dutch queen who holds the title of prince rather than king and supports the monarch in ceremonial, representative, and advisory roles without exercising sovereign authority.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.