Triple
T20613611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah (Book of Tobit) |
E506508
|
entity |
| Predicate | prayerHeardSimultaneouslyWith |
P140776
|
FINISHED |
| Object | Tobit’s 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: Tobit’s prayer | Statement: [Sarah (Book of Tobit), prayerHeardSimultaneouslyWith, Tobit’s prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerHeardSimultaneouslyWith Context triple: [Sarah (Book of Tobit), prayerHeardSimultaneouslyWith, Tobit’s prayer]
-
A.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
-
B.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
C.
praysIn
Indicates that an entity performs the act of praying within or at a particular place or setting.
-
D.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
E.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aada19e481909363428ceda67603 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.