Triple
T14172234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aemilii Paulli |
E351236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman family branch |
C13505
|
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: ancient Roman family branch Context triple: [Aemilii Paulli, instanceOf, ancient Roman family branch]
-
A.
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.
-
B.
member of the Roman imperial family
A member of the Roman imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to succession within the Roman Empire.
-
C.
member of the Julii family
A member of the Julii family is an individual belonging to the ancient Roman patrician gens Julia, sharing its lineage, social status, and familial identity.
-
D.
Italian dynasty
An Italian dynasty is a hereditary ruling family originating from Italy that maintains political, social, or economic power across multiple generations.
-
E.
Roman cognomen
chosen
A Roman cognomen is the third part of a traditional Roman male name, originally a nickname that evolved into a hereditary family branch identifier within a gens.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:01 a.m.