Triple
T34866168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tumba de Amelia Goyri (La Milagrosa) |
E1005015
|
entity |
| Predicate | esVeneradaComo |
P137926
|
FINISHED |
| Object | tumba milagrosa |
—
|
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: tumba milagrosa | Statement: [tumba de Amelia Goyri (La Milagrosa), esVeneradaComo, tumba milagrosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esVeneradaComo Context triple: [tumba de Amelia Goyri (La Milagrosa), esVeneradaComo, tumba milagrosa]
-
A.
isVeneratedAs
chosen
Indicates that one entity is regarded and honored by others as sacred, holy, or worthy of deep reverence.
-
B.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
D.
veneratedOn
Indicates that an entity is honored, revered, or celebrated on a specific date or occasion.
-
E.
unitesVenerationOf
Indicates that one entity brings together or combines the acts or practices of veneration directed toward multiple entities into a unified form.
- 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_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.