Triple
T14723649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marianne of the Netherlands |
E345878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Orange-Nassau member |
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: House of Orange-Nassau member Context triple: [Marianne of the Netherlands, instanceOf, House of Orange-Nassau member]
-
A.
member of the House of Nassau
A member of the House of Nassau is an individual belonging by birth or lawful adoption to the historic European noble dynasty of Nassau, associated with various principalities and modern royal families, notably in the Netherlands and Luxembourg.
-
B.
member of the Dutch royal family by marriage
A member of the Dutch royal family by marriage is an individual who acquires royal status and associated roles through legally recognized union with a born or reigning member of the Dutch royal house.
-
C.
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.
-
D.
Luxembourg dynasty member
A Luxembourg dynasty member is an individual belonging to the medieval European royal House of Luxembourg, which produced several Holy Roman Emperors, kings, and high-ranking nobles.
-
E.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.