Triple
T31702075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurus |
E809082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman surname |
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 surname Context triple: [Maurus, instanceOf, ancient Roman surname]
-
A.
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.
-
B.
Roman nomen gentilicium
A Roman nomen gentilicium is the hereditary family name that identifies an individual’s gens (clan) within the traditional three-part Roman naming system.
-
C.
Latin family name
A Latin family name is a hereditary surname of Latin origin, often derived from personal names, occupations, locations, or characteristic traits, used to identify and distinguish members of a family lineage.
-
D.
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.
-
E.
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.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:12 p.m.