Triple
T2439292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litany of Loreto |
E53235
|
entity |
| Predicate | responseFormula |
P39336
|
FINISHED |
| Object | Pray for us |
—
|
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: Pray for us | Statement: [Litany of Loreto, responseFormula, Pray for us]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseFormula Context triple: [Litany of Loreto, responseFormula, Pray for us]
-
A.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
B.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
C.
statusFormula
Indicates a formal expression or rule that defines or evaluates the current status or condition of something.
-
D.
reaction
Indicates a chemical or physical process in which one set of substances or conditions transforms into another, often involving interaction, change, or response between entities.
-
E.
petitionFormula
Indicates a formal written request or appeal made by one party to another, typically to an authority, following a specific formula or structured format.
- F. None of above. chosen
Provenance (4 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcebe7dd08190b197a2a0e78787e3 |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 6, 2026, 9:43 p.m.