Triple
T14520866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespasius Pollio |
E340645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Vespasii family |
C34895
|
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 Vespasii family Context triple: [Vespasius Pollio, instanceOf, member of the Vespasii 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 Julii Caesares
A member of the Julii Caesares is an individual belonging to the prominent patrician branch of the Roman gens Julia, associated with Gaius Julius Caesar and his close familial line.
-
C.
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.
-
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 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.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.