Triple
T1720935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Elizabeth of the United Kingdom |
E37387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Landgravine consort |
C9716
|
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: Landgravine consort Context triple: [Princess Elizabeth of the United Kingdom, instanceOf, Landgravine consort]
-
A.
Electress Palatine
An Electress Palatine was the wife or female consort of the Elector Palatine, a prince of the Holy Roman Empire who held the hereditary right to participate in the election of the emperor.
-
B.
Bavarian princess
A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
-
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.
Holy Roman Empress consort
A Holy Roman Empress consort is the wife of a reigning Holy Roman Emperor, holding the empire’s highest female title and often exercising ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
-
E.
Countess of Angoulême
The Countess of Angoulême is a noble title historically granted to the female ruler or consort associated with the County of Angoulême in southwestern France, often linked to influential medieval and early modern European dynasties.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.