Triple
T16386616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annius |
E397938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman nomen gentilicium |
C12598
|
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 nomen gentilicium Context triple: [Annius, instanceOf, ancient Roman nomen gentilicium]
-
A.
Roman nomen gentilicium
chosen
A Roman nomen gentilicium is the hereditary family name that identifies an individual’s gens (clan) within the traditional three-part Roman naming system.
-
B.
Roman cognomen
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.
-
C.
Roman name
A Roman name is a personal designation used in ancient Rome, typically composed of multiple parts (such as praenomen, nomen, and cognomen) that indicated an individual's given name, family lineage, and sometimes personal traits or achievements.
-
D.
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.
-
E.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.