Triple
T34866181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tumba de Amelia Goyri (La Milagrosa) |
E1005015
|
entity |
| Predicate | tieneRitualAsociado |
P4193
|
FINISHED |
| Object | golpear suavemente la tumba |
—
|
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: golpear suavemente la tumba | Statement: [tumba de Amelia Goyri (La Milagrosa), tieneRitualAsociado, golpear suavemente la tumba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneRitualAsociado Context triple: [tumba de Amelia Goyri (La Milagrosa), tieneRitualAsociado, golpear suavemente la tumba]
-
A.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
hasRitualSequence
Indicates that one ritual is ordered to occur before or after another within a defined ceremonial sequence.
-
D.
hasRitualDay
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
-
E.
hasRitualSystem
Indicates that an entity possesses or is associated with a structured set of rituals or ceremonial practices.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.