Triple
T1794891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Answered Prayers |
E39580
|
entity |
| Predicate | authorDiedBeforeCompletion |
P15628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Answered Prayers, authorDiedBeforeCompletion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorDiedBeforeCompletion Context triple: [Answered Prayers, authorDiedBeforeCompletion, true]
-
A.
yearOfAuthorDeathRelation
Indicates the specific year in which the referenced author died.
-
B.
isPosthumousWorkOf
chosen
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
C.
publishedAuthor
Indicates that a person is the author of one or more works that have been formally published.
-
D.
ceasedPublication
Indicates that an entity (such as a publication or series) has stopped being produced or released and is no longer ongoing.
-
E.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.