Triple
T4841533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scourging at the Pillar |
E108190
|
entity |
| Predicate | prayerIntention |
P59711
|
FINISHED |
| Object | strength to resist temptation |
—
|
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: strength to resist temptation | Statement: [Scourging at the Pillar, prayerIntention, strength to resist temptation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerIntention Context triple: [Scourging at the Pillar, prayerIntention, strength to resist temptation]
-
A.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
B.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
C.
associatedPrayerChange
Indicates a change in a prayer that is linked or connected to another entity, event, or condition.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
isAddressedInPrayer
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dfff1488190a32bbb615bfab970 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:25 p.m.