Triple
T8950134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Licinius Crassus |
E213323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Roman senatorial class |
C6905
|
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 Roman senatorial class Context triple: [Marcus Licinius Crassus, instanceOf, member of the Roman senatorial class]
-
A.
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.
-
B.
Roman senator
chosen
A Roman senator is a high-ranking political figure in ancient Rome who participates in legislative, advisory, and administrative decision-making within the Senate, influencing the governance and policies of the Roman state.
-
C.
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.
-
D.
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.
-
E.
member of the Roman equestrian order
A member of the Roman equestrian order was a wealthy, property-owning citizen of the second-highest social class in ancient Rome, ranking below senators and often serving in administrative, financial, and military roles.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:59 p.m.