Triple

T11616288
Position Surface form Disambiguated ID Type / Status
Subject Hamilcar I of Carthage E275517 entity
Predicate instanceOf P0 FINISHED
Object member of the Magonid dynasty C30773 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 Magonid dynasty
Context triple: [Hamilcar I of Carthage, instanceOf, member of the Magonid dynasty]
  • A. member of the Battiad dynasty
    A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
  • B. member of the Deinomenid dynasty
    A member of the Deinomenid dynasty is an individual belonging to the ruling family that controlled Syracuse and parts of Sicily in the early 5th century BCE, originating from the tyrant Gelon and his relatives.
  • C. Salian dynasty member
    A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
  • D. member of the Theodosian dynasty
    A member of the Theodosian dynasty is an individual belonging to the late Roman imperial family founded by Emperor Theodosius I, which ruled parts of the Roman Empire from the late 4th to the mid-5th century CE.
  • E. Herodian dynasty member
    A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
  • 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_69d6aaf84b548190ac072e4fb89ae18f completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 9:38 p.m.