Triple
T8436755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieter van Vollenhoven |
E199245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Dutch royal family by marriage |
C24376
|
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: member of the Dutch royal family by marriage Context triple: [Pieter van Vollenhoven, instanceOf, member of the Dutch royal family by marriage]
-
A.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
B.
member of extended royal family
A member of the extended royal family is an individual related by blood, marriage, or adoption to the reigning monarch or core royal line, but who holds a more distant position in the line of succession and typically fewer official duties.
-
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.
princess consort of Orange
A princess consort of Orange is the wife of the reigning Prince of Orange, holding the title by marriage rather than by birth or sovereign right.
-
E.
Belgian princess
A Belgian princess is a female member of the Belgian royal family, typically the daughter or close female relative of the reigning monarch or heir to the throne, who may undertake ceremonial, diplomatic, and charitable duties on behalf of the kingdom.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:08 p.m.