Triple
T6374041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Joséphine-Charlotte of Belgium |
E143418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Duchess consort of Luxembourg |
C15528
|
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: Grand Duchess consort of Luxembourg Context triple: [Princess Joséphine-Charlotte of Belgium, instanceOf, Grand Duchess consort of Luxembourg]
-
A.
Grand Duchess of Luxembourg
chosen
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.
-
B.
duchess consort of Parma
A duchess consort of Parma is the wife of the reigning Duke of Parma, holding the title and ceremonial duties of duchess without exercising sovereign authority.
-
C.
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.
-
D.
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.
-
E.
Countess consort of Guelders
A Countess consort of Guelders is the wife of the reigning Count of Guelders, holding the title and associated social status through marriage rather than by hereditary right.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:33 p.m.