Triple
T30996141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calanda |
E789801
|
entity |
| Predicate | hasHolyWeekPractice |
P190677
|
FINISHED |
| Object | collective drumming |
—
|
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: collective drumming | Statement: [Calanda, hasHolyWeekPractice, collective drumming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolyWeekPractice Context triple: [Calanda, hasHolyWeekPractice, collective drumming]
-
A.
hasPilgrimageOrFeast
Indicates that there is a religious pilgrimage or feast associated with, dedicated to, or occurring in relation to the referenced entity.
-
B.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
C.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
D.
isHolyDayFor
Indicates that a particular day is recognized or observed as a religiously significant or sacred day for a given entity or group.
-
E.
hasRitualDay
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 29, 2026, 8:56 p.m.