Triple
T35320453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gens Vinicia |
E1020024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman senatorial family |
C61545
|
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 senatorial family Context triple: [gens Vinicia, instanceOf, Roman senatorial family]
-
A.
Roman aristocratic lineage
chosen
A Roman aristocratic lineage is a hereditary elite family line in ancient Rome, distinguished by noble ancestry, political influence, social prestige, and the transmission of status, wealth, and public offices across generations.
-
B.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
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.
ancient Roman family
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.
-
E.
Sicilian noble family
A Sicilian noble family is an aristocratic lineage rooted in Sicily, historically distinguished by hereditary titles, landownership, and influence over regional politics, culture, and social life.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.