Triple
T27325970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Dorothea of Württemberg |
E689644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian empress consort |
C1535
|
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: Russian empress consort Context triple: [Sophie Dorothea of Württemberg, instanceOf, Russian empress consort]
-
A.
Empress consort of Russia
chosen
The Empress consort of Russia was the wife of the reigning Russian emperor (tsar), holding a high ceremonial and social status at court, often influencing politics, culture, and dynastic affairs without ruling in her own right.
-
B.
Electress consort
An electress consort is the wife of a ruling prince-elector in the Holy Roman Empire, holding the ceremonial and social status associated with her husband's electoral dignity.
-
C.
empress consort of the French
The empress consort of the French is the wife of a reigning Emperor of the French, holding the highest female rank at court and serving as his ceremonial and often political partner without exercising sovereign authority in her own right.
-
D.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
-
E.
Duchess consort of Holstein-Gottorp
The Duchess consort of Holstein-Gottorp is the wife of the reigning Duke of Holstein-Gottorp, holding a ceremonial and dynastic role within the ducal house and its associated European noble networks.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:35 a.m.