Triple
T9311200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anicius Probinus (probable) |
E224009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Anicii family |
C23543
|
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 Anicii family Context triple: [Anicius Probinus (probable), instanceOf, member of the Anicii family]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
member of the Roman nobility
chosen
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
-
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.
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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.