Triple
T17858912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William, Prince of Orange |
E446013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heir to the throne of the Netherlands |
C13919
|
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: heir to the throne of the Netherlands Context triple: [William, Prince of Orange, instanceOf, heir to the throne of the Netherlands]
-
A.
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.
-
B.
Dutch royal
chosen
A Dutch royal is a member of the Netherlands' reigning House of Orange-Nassau, holding constitutional, ceremonial, and representative roles within the Dutch monarchy.
-
C.
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.
-
D.
representative of the Dutch monarch
A representative of the Dutch monarch is an official, such as the King's Commissioner or a royal envoy, who acts on behalf of the King of the Netherlands in specific regions or functions, carrying out ceremonial, administrative, or diplomatic duties.
-
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.
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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:17 a.m.