Triple
T34381851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of Knock |
E882458
|
entity |
| Predicate | inspiredHymn |
P28252
|
FINISHED |
| Object | Our Lady of Knock (hymn) |
—
|
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: Our Lady of Knock (hymn) | Statement: [Our Lady of Knock, inspiredHymn, Our Lady of Knock (hymn)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredHymn Context triple: [Our Lady of Knock, inspiredHymn, Our Lady of Knock (hymn)]
-
A.
inspiredSong
chosen
Indicates that one entity (such as an event, person, or work) served as the creative inspiration or motivating influence for the creation of a particular song.
-
B.
isInspirationalSong
Indicates that a song motivates, uplifts, or positively influences listeners through its message, emotion, or impact.
-
C.
inspiredEmotion
Indicates that one entity has caused or stimulated a particular emotion or emotional state in another entity.
-
D.
hymnsDedicatedTo
Indicates that certain hymns are specifically devoted or addressed to a particular entity as their subject or object of veneration.
-
E.
associatedWithHymns
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:59 a.m.