Triple
T35861904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Calpurnius Piso (consul of AD 57) |
E1036973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Calpurnius Piso family member |
C33490
|
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: Calpurnius Piso family member Context triple: [Lucius Calpurnius Piso (consul of AD 57), instanceOf, Calpurnius Piso family member]
-
A.
member of the Calpurnii Pisones
chosen
A member of the Calpurnii Pisones is an individual belonging to the prominent Roman aristocratic family (gens Calpurnia), specifically its influential Piso branch, often associated with high political office and cultural patronage in the late Republic and early Empire.
-
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 gens Pompeia
A member of the gens Pompeia is an individual belonging by birth or adoption to the ancient Roman plebeian family Pompeia, sharing its name, lineage, and social identity within Roman society.
-
D.
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.
-
E.
member of the Domitii Ahenobarbi
A member of the Domitii Ahenobarbi is an individual belonging to the ancient Roman aristocratic family (gens Domitia) distinguished by the cognomen Ahenobarbus, traditionally associated with their characteristic "bronze-bearded" lineage.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.