Triple
T19748665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorare prayer |
E474317
|
entity |
| Predicate | commonlyRecitedFor |
P112504
|
FINISHED |
| Object | urgent needs |
—
|
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: urgent needs | Statement: [Memorare prayer, commonlyRecitedFor, urgent needs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyRecitedFor Context triple: [Memorare prayer, commonlyRecitedFor, urgent needs]
-
A.
isOftenRecitedFor
chosen
Indicates that something (such as a text, phrase, or piece of music) is frequently spoken, chanted, or performed for a particular purpose, audience, or occasion.
-
B.
commonlyMemorized
Indicates that something is typically learned by heart and retained in memory by many people.
-
C.
recites
Indicates that one entity verbally delivers or repeats from memory the words, text, or performance associated with another entity.
-
D.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
-
E.
oftenCitedAs
Indicates that one entity is frequently referenced or mentioned as an example, source, or authority in relation to 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.