Triple
T33722212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murcia |
E864047
|
entity |
| Predicate | religiousProcession |
P6086
|
FINISHED |
| Object | Holy Week processions |
—
|
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: Holy Week processions | Statement: [Murcia, religiousProcession, Holy Week processions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousProcession Context triple: [Murcia, religiousProcession, Holy Week processions]
-
A.
ceremonialProcession
chosen
Indicates a formal, often ritualized movement of people or objects in an organized sequence as part of a ceremony or official event.
-
B.
organizesProcessions
Indicates that an entity is responsible for planning, coordinating, and managing the execution of processions or parades.
-
C.
hasProcessionDuring
Indicates that a procession or ceremonial march takes place during a specified time period or event.
-
D.
mainProcessionType
Indicates the primary category or kind of procession associated with an event or context.
-
E.
returnProcession
Indicates a movement or sequence of entities traveling back to a prior location or state, typically as part of a formal or organized return.
- F. None of above.
Provenance (3 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:44 a.m.