Triple
T15849322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deification of Julius Caesar |
E384294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman religious event |
C13466
|
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 religious event Context triple: [deification of Julius Caesar, instanceOf, Roman religious event]
-
A.
event in ancient Rome
chosen
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.
-
B.
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.
-
C.
Greek religious festival
A Greek religious festival is a recurring communal celebration in ancient Greek society that combines ritual worship of specific deities with processions, sacrifices, athletic or artistic competitions, and feasting to honor the gods and reinforce civic and religious identity.
-
D.
Roman mystery cult deity
A Roman mystery cult deity is a divine figure worshiped in secretive, initiatory religious groups within the Roman world, promising personal salvation, esoteric knowledge, or special favor to devoted adherents.
-
E.
Roman theatre
A Roman theatre is a large, semi-circular open-air structure designed for public performances, featuring tiered seating, an orchestra, and an elaborately decorated stage building.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.