Triple
T14979687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domitii Ahenobarbi family |
E373541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman noble lineage |
C23541
|
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: Roman noble lineage Context triple: [Domitii Ahenobarbi family, instanceOf, Roman noble lineage]
-
A.
Roman aristocrat
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political influence, owns extensive land and slaves, and upholds traditional social and cultural norms of the elite.
-
B.
Roman aristocrat
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political, social, and economic power through land ownership, patronage networks, and participation in public life.
-
C.
member of the Roman nobility
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
-
D.
Gallo-Roman aristocrat
A Gallo-Roman aristocrat is a wealthy, landowning elite of Romanized Gaul who blended Roman political, cultural, and social practices with local Gallic traditions to maintain regional power and influence.
-
E.
ancient Roman family
chosen
An ancient Roman family (familia) was a hierarchical household unit centered on the paterfamilias, encompassing blood relatives, adopted members, slaves, and clients bound together by legal authority, religious rites, and shared social status.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:51 a.m.