Triple
T4193174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcanalia |
E89081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman religious festival |
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: ancient Roman religious festival Context triple: [Vulcanalia, instanceOf, ancient Roman religious festival]
-
A.
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.
-
B.
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.
-
C.
Celtic festival
A Celtic festival is a cultural celebration featuring traditional music, dance, storytelling, crafts, and rituals that honor the heritage, mythology, and seasonal cycles of Celtic peoples.
-
D.
religious festival
A religious festival is a recurring, community-based celebration rooted in spiritual beliefs and traditions, marked by rituals, ceremonies, and social gatherings that honor deities, sacred events, or religious values.
-
E.
Athenian festival
An Athenian festival is a recurring public religious celebration in ancient Athens that combines ritual worship, processions, performances, and communal activities to honor specific gods, heroes, or civic ideals.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:46 p.m.