Triple
T30188790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchess Joséphine-Charlotte of Luxembourg |
E767413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | princess of Belgium |
C5185
|
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 Belgium Context triple: [Grand Duchess Joséphine-Charlotte of Luxembourg, instanceOf, princess of Belgium]
-
A.
Belgian princess
chosen
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.
-
B.
Grand Duchess of Luxembourg
The Grand Duchess of Luxembourg is the title held by the female sovereign or consort of the Grand Duke, serving as a central figure in the grand ducal family and the ceremonial life of the Grand Duchy of Luxembourg.
-
C.
prince of Belgium
A prince of Belgium is a male member of the Belgian royal family, typically a son or close male-line descendant of the reigning monarch or a former monarch, who holds the title "Prince of Belgium" by birth or royal decree.
-
D.
princess of Waldeck and Pyrmont
A princess of Waldeck and Pyrmont is a female member of the German princely House of Waldeck and Pyrmont, typically by birth or marriage, bearing the associated noble title and status.
-
E.
princess of Lorraine
A princess of Lorraine is a female member of the noble House of Lorraine, typically bearing the title by birth or marriage within this historic European ducal dynasty.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:28 p.m.