Triple
T32847504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Junius Brutus Damasippus |
E840140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the gens Junia |
C61497
|
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 Junia Context triple: [Lucius Junius Brutus Damasippus, instanceOf, member of the gens Junia]
-
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.
member of the gens Octavia
A "member of the gens Octavia" is an individual belonging by birth or adoption to the ancient Roman plebeian family (gens) Octavia, historically associated with figures such as Augustus.
-
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 Fabia
A member of the gens Fabia is an individual belonging to the ancient Roman patrician family Fabia, known for its political influence, military leadership, and recurring prominence in the Roman Republic’s history.
-
E.
member of the gens Munatia
A member of the gens Munatia is an individual belonging to the ancient Roman Munatia family, identified by shared nomen and lineage within that plebeian gens.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:17 a.m.