Triple
T23659712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richenza of Saxony |
E584409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of ducal house of Saxony |
C47922
|
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: member of ducal house of Saxony Context triple: [Richenza of Saxony, instanceOf, member of ducal house of Saxony]
-
A.
member of the House of Wettin
A member of the House of Wettin is an individual belonging to the historic German noble and royal dynasty that ruled various central European territories, including Saxony and Poland, over many centuries.
-
B.
member of the House of Reuss
A member of the House of Reuss is an individual belonging to the historic German princely family that ruled various small states in Thuringia, traditionally naming all male members Heinrich (Henry).
-
C.
member of the House of Ascania
A member of the House of Ascania is an individual belonging to the medieval German noble dynasty that ruled various principalities and territories, including Anhalt and Brandenburg, across several centuries.
-
D.
member of the House of Hesse-Kassel
A member of the House of Hesse-Kassel is an individual belonging to the German princely dynasty that ruled the Landgraviate and later Electorate of Hesse-Kassel, a branch of the larger House of Hesse.
-
E.
member of the House of Mecklenburg-Schwerin
A member of the House of Mecklenburg-Schwerin is an individual belonging by birth or lawful adoption to the historic German ducal and later grand ducal dynasty that ruled the territory of Mecklenburg-Schwerin.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.