Triple
T31199431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servius Cornelius Cethegus |
E795427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Cornelii |
C24998
|
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 Cornelii Context triple: [Servius Cornelius Cethegus, instanceOf, member of the Cornelii]
-
A.
member of the gens Cornelia
chosen
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.
-
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 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.
-
D.
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.
-
E.
member of the Calpurnii Pisones
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.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.