Triple
T10100064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Mecklenburg-Strelitz |
E216176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German ducal dynasty |
C12506
|
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: German ducal dynasty Context triple: [House of Mecklenburg-Strelitz, instanceOf, German ducal dynasty]
-
A.
German princely dynasty
chosen
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
B.
House of Wettin
The House of Wettin is a historic European noble dynasty originating in Saxony that produced numerous princes, electors, kings, and other rulers across central and northern Europe from the Middle Ages onward.
-
C.
House of Hesse and by Rhine
The House of Hesse and by Rhine was a German grand ducal dynasty that ruled the Grand Duchy of Hesse (centered on Darmstadt) from the early 19th century until the end of the German monarchies in 1918.
-
D.
House of Hesse-Kassel
The House of Hesse-Kassel was a German princely dynasty that ruled the Landgraviate (and later Electorate) of Hesse-Kassel, playing a significant political and military role in the Holy Roman Empire and later German states.
-
E.
German noble family branch
A German noble family branch is a distinct lineage or subdivision of a larger aristocratic house in German-speaking regions, typically defined by shared ancestry, territorial holdings, and hereditary titles.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:02 p.m.