Triple
T30170062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Year festival in Babylon |
E766895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Babylonian festival |
C25301
|
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: Babylonian festival Context triple: [New Year festival in Babylon, instanceOf, Babylonian festival]
-
A.
Mesopotamian festival
chosen
A Mesopotamian festival is a recurring religious and civic celebration in ancient Mesopotamia that honored specific deities through rituals, processions, offerings, and communal feasting, reinforcing cosmic order and social cohesion.
-
B.
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.
-
C.
Babylonian god
A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
-
D.
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.
-
E.
Mesopotamian month
A Mesopotamian month is a lunar-based time unit in ancient Mesopotamian calendars, typically beginning with the first visible crescent of the moon and used to structure religious festivals, agricultural activities, and administrative records.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:24 p.m.