Triple
T3185185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma of Waldeck and Pyrmont |
E66681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | princess of Waldeck and Pyrmont |
C12408
|
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 Waldeck and Pyrmont Context triple: [Emma of Waldeck and Pyrmont, instanceOf, princess of Waldeck and Pyrmont]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.