Triple

T31910497
Position Surface form Disambiguated ID Type / Status
Subject Anicius Hermogenianus Olybrius E814668 entity
Predicate instanceOf P0 FINISHED
Object member of the Anician family C61271 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 Anician family
Context triple: [Anicius Hermogenianus Olybrius, instanceOf, member of the Anician family]
  • A. member of the Vespasii family
    A member of the Vespasii family is an individual belonging to the Roman gens Vespasia, a prominent family best known for producing the emperor Vespasian and his imperial Flavian dynasty.
  • B. member of the Roman imperial family
    A member of the Roman imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to succession within the Roman Empire.
  • C. member of the Julii family
    A member of the Julii family is an individual belonging to the ancient Roman patrician gens Julia, sharing its lineage, social status, and familial identity.
  • D. member of the Severan dynasty
    A member of the Severan dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 193 to 235 CE, beginning with Septimius Severus and including his successors such as Caracalla, Elagabalus, and Severus Alexander.
  • E. member of the Constantinian dynasty
    A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
  • 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_69f348f109d88190b5005372c53d2fcd completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:01 a.m.