Triple
T3362364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Aemilius Paullus |
E70751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the gens Aemilia |
C12649
|
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 gens Aemilia Context triple: [Lucius Aemilius Paullus, instanceOf, member of the gens Aemilia]
-
A.
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.
-
B.
Roman consul
A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
-
C.
Roman senator
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.
-
D.
member of the Flavian dynasty
A member of the Flavian dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 69 to 96 CE, including emperors Vespasian, Titus, and Domitian and their close relatives.
-
E.
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.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.