Triple
T17796267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Cecilie of Greece and Denmark |
E444300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Duchess of Hesse |
C39160
|
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 of Hesse Context triple: [Princess Cecilie of Greece and Denmark, instanceOf, Grand Duchess of Hesse]
-
A.
Grand Duchess consort of Mecklenburg-Strelitz
The Grand Duchess consort of Mecklenburg-Strelitz is the wife of the reigning Grand Duke of Mecklenburg-Strelitz, serving as his royal consort and participating in the ceremonial, social, and dynastic duties of the grand ducal court.
-
B.
duchess of Bavaria
A duchess of Bavaria is a noblewoman who holds the hereditary or marital title associated with the ducal rulership of the historical region of Bavaria within the Holy Roman Empire and later German states.
-
C.
Duchess of Brunswick-Lüneburg
A Duchess of Brunswick-Lüneburg is a noblewoman who holds the ducal title in the historical German principality of Brunswick-Lüneburg, typically by marriage to or inheritance from a reigning duke.
-
D.
Electress of Bavaria
The Electress of Bavaria was the title held by the consort of the Elector of Bavaria, a principal ruler within the Holy Roman Empire who possessed the hereditary right to participate in the election of the emperor.
-
E.
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.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:13 a.m.