Triple
T33107943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JohnsPrayerForHealthAndWellBeing |
E847242
|
entity |
| Predicate | requestsFromGod |
P175569
|
FINISHED |
| Object | health for Gaius |
—
|
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: health for Gaius | Statement: [JohnsPrayerForHealthAndWellBeing, requestsFromGod, health for Gaius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestsFromGod Context triple: [JohnsPrayerForHealthAndWellBeing, requestsFromGod, health for Gaius]
-
A.
requestedDevotion
Indicates that one entity has asked another entity to show or commit a particular form or level of devotion.
-
B.
missionFromGod
Indicates that an entity is carrying out a task or purpose believed to be assigned or authorized by a divine being.
-
C.
spokeToJesusAbout
Indicates that one entity communicated verbally with Jesus regarding a particular topic or matter.
-
D.
divineInteraction
Indicates an interaction or exchange occurring between a divine being (or force) and another entity.
-
E.
raisedByGod
Indicates that an entity has been brought back to life or elevated in status through the direct action or power of God.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e86f7c8190836278fd08e5cfed |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d30b9e048190b0982e30b7fdfa3c |
completed | May 3, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:26 a.m.