Triple
T18373836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgen del Rosario |
E446256
|
entity |
| Predicate | devotionPracticedBy |
P130883
|
FINISHED |
| Object | Catholics worldwide |
—
|
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: Catholics worldwide | Statement: [Virgen del Rosario, devotionPracticedBy, Catholics worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionPracticedBy Context triple: [Virgen del Rosario, devotionPracticedBy, Catholics worldwide]
-
A.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
C.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
D.
evidenceOfDevotion
Indicates that one entity serves as proof or demonstration of another entity’s devotion or commitment.
-
E.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517561edc8190b5d2834707ab662b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:45 a.m.