Triple
T18899058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | family of Germanicus |
E462288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Julio-Claudian dynasty branch |
C14509
|
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: Julio-Claudian dynasty branch Context triple: [family of Germanicus, instanceOf, Julio-Claudian dynasty branch]
-
A.
member of the Flavian dynasty
A member of the Flavian dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 69 to 96 CE, including emperors Vespasian, Titus, and Domitian and their close relatives.
-
B.
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.
-
C.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
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.
dynastic branch
chosen
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:58 a.m.