Triple
T7770754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kukulcán |
E179061
|
entity |
| Predicate | ritualEvent |
P78238
|
FINISHED |
| Object | equinox serpent-shadow phenomenon |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: equinox serpent-shadow phenomenon | Statement: [Kukulcán, ritualEvent, equinox serpent-shadow phenomenon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualEvent Context triple: [Kukulcán, ritualEvent, equinox serpent-shadow phenomenon]
-
A.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
B.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
C.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
D.
partOfRitual
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
E.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
- F. None of above. chosen
Provenance (4 batches)
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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70438ca2481909114b0c434717109 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702a78edc819090c3448d33c8c381 |
completed | March 27, 2026, 10:20 p.m. |
Created at: March 27, 2026, 4:11 p.m.