Triple
T32541381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feriae Latinae |
E831721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state festival of ancient Rome |
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: state festival of ancient Rome Context triple: [Feriae Latinae, instanceOf, state festival of ancient Rome]
-
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 festival of Venus
A Roman festival of Venus is a religious celebration in ancient Rome dedicated to honoring the goddess Venus through rituals, offerings, and public festivities that emphasized love, beauty, fertility, and social harmony.
-
C.
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.
-
D.
Phrygian festival
A Phrygian festival is a celebratory event in ancient Phrygian culture, typically involving religious rites, music, dance, and communal gatherings in honor of deities such as Cybele.
-
E.
Spartan festival
A Spartan festival is a religious and civic celebration in ancient Sparta that combined ritual worship, athletic and musical competitions, communal feasting, and displays of military discipline to reinforce social cohesion and Spartan values.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.