Triple
T24968708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess Palatine Maria Franziska of Sulzbach |
E624818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess Palatine |
C49356
|
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: Countess Palatine Context triple: [Countess Palatine Maria Franziska of Sulzbach, instanceOf, Countess Palatine]
-
A.
Countess of Holland
The Countess of Holland is a noble title historically held by the wife or female ruler associated with the medieval County of Holland in the Low Countries, signifying high aristocratic status and territorial influence.
-
B.
Countess of Hainaut
The Countess of Hainaut is a noblewoman who holds, by birth or marriage, the comital title associated with the medieval County of Hainaut, historically located in what is now parts of Belgium and northern France.
-
C.
Duchess of Leuchtenberg
The Duchess of Leuchtenberg is a noble title historically associated with the consort or female holder within the Leuchtenberg branch of the Beauharnais family, linked to European aristocracy and often tied to dynastic alliances.
-
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.
Countess of Burgundy
The Countess of Burgundy is a noblewoman who holds or is married to the holder of the feudal title governing the historic County of Burgundy, wielding significant regional authority, land rights, and dynastic influence.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6 a.m.