Triple
T750185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary, Princess Royal and Princess of Orange |
E15429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Princess of Orange |
C4568
|
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: Princess of Orange Context triple: [Mary, Princess Royal and Princess of Orange, instanceOf, Princess of Orange]
-
A.
Prince of Orange
The Prince of Orange is a hereditary noble title historically associated with the sovereign rulers of the Principality of Orange and later with the heir apparent to the Dutch throne.
-
B.
Princess Royal
Princess Royal is a conceptual class representing the eldest daughter of a reigning monarch, typically holding a ceremonial title that signifies her high rank and specific duties within the royal family.
-
C.
Queen of the Netherlands
The Queen of the Netherlands is the female monarch who serves as the ceremonial head of state of the Kingdom of the Netherlands, representing national unity and continuity within its constitutional monarchy.
-
D.
Queen of Bohemia
The Queen of Bohemia is the reigning or consort monarch of the historical Kingdom of Bohemia, embodying its royal authority, cultural identity, and dynastic alliances within Central Europe.
-
E.
Austrian archduchess
An Austrian archduchess is a female member of the Habsburg or Habsburg-Lorraine dynasty, traditionally bearing the noble title associated with the Archduchy of Austria and often involved in dynastic politics, court life, and diplomatic marriages.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.