Triple

T25760607
Position Surface form Disambiguated ID Type / Status
Subject Universal Prayer E648729 entity
Predicate commonResponseFormula P68576 FINISHED
Object Lord, hear our prayer 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: Lord, hear our prayer | Statement: [Universal Prayer, commonResponseFormula, Lord, hear our prayer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonResponseFormula
Context triple: [Universal Prayer, commonResponseFormula, Lord, hear our prayer]
  • A. typicalResponseFormula chosen
    Indicates that there is a standard or characteristic formula that typically represents the response associated with the given entities or situation.
  • B. responseFormula
    Indicates that one entity’s reaction, reply, or outcome is expressed or encoded in a specific formula or structured representation.
  • C. responseLanguageFormula
    Indicates that one entity specifies or encodes the language or linguistic form in which another entity’s response, expression, or output is formulated.
  • D. formulaUsed
    Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
  • E. formulaType
    Indicates the specific kind or category of formula associated with an entity or expression.
  • 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_69e7ab322db0819092d6a2b3d4572e01 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 22, 2026, 5:05 a.m.