Triple
T27142204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock Shrine |
E681843
|
entity |
| Predicate | hasPrimaryDevotionTo |
P21326
|
FINISHED |
| Object | Blessed Virgin Mary |
—
|
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: Blessed Virgin Mary | Statement: [Knock Shrine, hasPrimaryDevotionTo, Blessed Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryDevotionTo Context triple: [Knock Shrine, hasPrimaryDevotionTo, Blessed Virgin Mary]
-
A.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
B.
associatedDevotion
chosen
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
C.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
D.
devotionPracticedBy
Indicates that a particular form of devotion, worship, or religious practice is performed or carried out by a specified agent or practitioner.
-
E.
hasDevotionalRole
Indicates that an entity holds or performs a specific role or function within a devotional or religious practice.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 27, 2026, 9:10 a.m.