Triple
T30161862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aemilii Scauri family |
E766687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of gens Aemilia |
C54575
|
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: branch of gens Aemilia Context triple: [Aemilii Scauri family, instanceOf, branch of gens Aemilia]
-
A.
member of the gens Aemilia
A member of the gens Aemilia is an individual belonging to the ancient Roman patrician family Aemilia, known for its political influence, consular magistracies, and longstanding prominence in Roman public life.
-
B.
branch of Roman gens
chosen
A branch of a Roman gens is a subordinate family line within a larger clan, typically distinguished by a specific cognomen and shared ancestry.
-
C.
patrician branch of gens Junia
The patrician branch of the gens Junia was an aristocratic lineage within the ancient Roman Junian clan, distinguished by its early elevation to patrician status and its members’ prominence in the Republic’s political and religious offices.
-
D.
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.
-
E.
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.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:22 p.m.