Triple
T32004125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caristia |
E817214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman family celebration |
C23541
|
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: Roman family celebration Context triple: [Caristia, instanceOf, Roman family celebration]
-
A.
ancient Roman family
chosen
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.
Roman musical gathering
A Roman musical gathering is a social event in ancient Rome where participants assemble in a domestic or public setting to enjoy live performances of vocal and instrumental music, often accompanied by poetry, dining, and conversation.
-
C.
Roman imperial household
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
D.
event in ancient Rome
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
-
E.
Roman cult
A Roman cult is a religious group or practice in ancient Rome centered on the worship of a specific deity, emperor, or sacred concept, involving prescribed rituals, offerings, and communal observances.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:14 a.m.