Triple
T11234688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onesiphorus |
E265911
|
entity |
| Predicate | subjectOfPrayerIn |
P11162
|
FINISHED |
| Object | 2 Timothy 1:16–18 |
—
|
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: 2 Timothy 1:16–18 | Statement: [Onesiphorus, subjectOfPrayerIn, 2 Timothy 1:16–18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfPrayerIn Context triple: [Onesiphorus, subjectOfPrayerIn, 2 Timothy 1:16–18]
-
A.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
B.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
isAddressedInPrayer
chosen
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
-
D.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
E.
regardsPrayerAs
Indicates that one entity holds a particular attitude, evaluation, or characterization toward prayer as a practice or concept.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.