Triple

T30947891
Position Surface form Disambiguated ID Type / Status
Subject Johann August of Saxe-Gotha-Altenburg E788448 entity
Predicate instanceOf P0 FINISHED
Object member of the Ernestine line C12082 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 the Ernestine line
Context triple: [Johann August of Saxe-Gotha-Altenburg, instanceOf, member of the Ernestine line]
  • A. member of the House of Wettin chosen
    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 ducal house of Saxony
    A member of the ducal house of Saxony is an individual belonging by birth or legitimate lineage to the noble family that historically held the ducal title and ruled or represented the Duchy of Saxony.
  • C. 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).
  • D. member of the House of Hesse-Darmstadt
    A member of the House of Hesse-Darmstadt is an individual belonging by birth or marriage to the German princely dynasty that historically ruled the Landgraviate and later Grand Duchy of Hesse-Darmstadt.
  • E. member of the House of Welf
    A member of the House of Welf is an individual belonging by birth or legitimate adoption to the historic European noble dynasty known as the Welfs, which has produced numerous dukes, princes, and monarchs.
  • 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_69f224c180f88190ad177372ee02b7e2 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:53 p.m.