Triple
T28824793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Calpurnius Piso Caesoninus |
E727871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Calpurnia gens |
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: member of the Calpurnia gens Context triple: [Lucius Calpurnius Piso Caesoninus, instanceOf, member of the Calpurnia gens]
-
A.
member of the gens Claudia
A member of the gens Claudia is an individual belonging to the ancient Roman patrician (and later plebeian) family Claudia, known for its prominent political, military, and social influence in the Roman Republic and Empire.
-
B.
member of the Sempronia gens
A member of the Sempronia gens is an individual belonging to the ancient Roman Sempronia family, a plebeian gens known for producing several notable politicians and military leaders.
-
C.
member of the gens Munatia
A member of the gens Munatia is an individual belonging to the ancient Roman Munatia family, identified by shared nomen and lineage within that plebeian gens.
-
D.
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.
-
E.
member of the gens Cornelia
A member of the gens Cornelia is an individual belonging to the prominent and influential Cornelii family of ancient Rome, known for producing many notable political and military leaders.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:35 a.m.