Triple
T13761402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberillus |
E330617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman child |
C12577
|
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 child Context triple: [Tiberillus, instanceOf, ancient Roman child]
-
A.
ancient Roman
chosen
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.
-
B.
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.
-
C.
Roman imperial princess
A Roman imperial princess is a female member of the emperor’s family whose status, marriages, and public image were used to secure dynastic legitimacy and political alliances within the Roman Empire.
-
D.
1st-century Roman woman
A 1st-century Roman woman is a female inhabitant of the Roman Empire during the first century CE, whose daily life, legal status, and social roles were shaped by Roman law, family structures, and cultural norms of the period.
-
E.
2nd-century Roman woman
A 2nd-century Roman woman is a female inhabitant of the Roman Empire during the 100s CE, whose daily life, legal status, and social roles were shaped by Roman family structures, class hierarchies, and regional cultural practices.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:09 p.m.