Triple
T27142206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock Shrine |
E681843
|
entity |
| Predicate | hasSecondaryDevotionTo |
P21326
|
FINISHED |
| Object | Saint Joseph |
—
|
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: Saint Joseph | Statement: [Knock Shrine, hasSecondaryDevotionTo, Saint Joseph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryDevotionTo Context triple: [Knock Shrine, hasSecondaryDevotionTo, Saint Joseph]
-
A.
hasSecondaryDeity
Indicates that an entity has an associated secondary or subordinate deity linked to it.
-
B.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
C.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
D.
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.
-
E.
hasSecondaryReligion
Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 9:10 a.m.