Triple
T25519694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth of Mecklenburg-Güstrow |
E639611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Mecklenburg member |
C50902
|
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: House of Mecklenburg member Context triple: [Elizabeth of Mecklenburg-Güstrow, instanceOf, House of Mecklenburg member]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
House of Hohenzollern member
A House of Hohenzollern member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories including Brandenburg-Prussia and the German Empire.
-
E.
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).
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:59 p.m.