Triple
T24993100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plateros |
E625497
|
entity |
| Predicate | hasDevotionalImage |
P59689
|
FINISHED |
| Object | Santo Niño de Atocha |
—
|
NE NERFINISHED |
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: Santo Niño de Atocha | Statement: [Plateros, hasDevotionalImage, Santo Niño de Atocha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotionalImage Context triple: [Plateros, hasDevotionalImage, Santo Niño de Atocha]
-
A.
hasDevotionalForm
Indicates that one entity takes or possesses a devotional expression, format, or mode in relation to another entity or context.
-
B.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
-
C.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
D.
devotionalObject
chosen
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
E.
devotionalCollection
Indicates that one entity is a curated set or compilation of devotional items, works, or practices associated with another entity.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 6:04 a.m.