Triple
T30330652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Cornelius Cinna |
E771467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Cornelii Cinnae |
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 Cinnae Context triple: [Gnaeus Cornelius Cinna, instanceOf, member of the Cornelii Cinnae]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
member of the gens Aemilia
A member of the gens Aemilia is an individual belonging to the ancient Roman patrician family Aemilia, known for its political influence, consular magistracies, and longstanding prominence in Roman public life.
-
E.
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.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:53 p.m.