Triple
T15683920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Domitius Ahenobarbus (consul 122 BC) |
E377647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Domitii Ahenobarbi |
C35714
|
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 Domitii Ahenobarbi Context triple: [Gnaeus Domitius Ahenobarbus (consul 122 BC), instanceOf, member of the Domitii Ahenobarbi]
-
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 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.
-
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 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.
-
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. 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:17 a.m.