Triple
T23292222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Way of Holiness |
E590061
|
entity |
| Predicate | impactOnReaders |
P95128
|
FINISHED |
| Object | encouraged pursuit of entire sanctification |
—
|
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: encouraged pursuit of entire sanctification | Statement: [The Way of Holiness, impactOnReaders, encouraged pursuit of entire sanctification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnReaders Context triple: [The Way of Holiness, impactOnReaders, encouraged pursuit of entire sanctification]
-
A.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
impactOnAuthor
Indicates that one entity has an effect, influence, or consequence on the author.
-
C.
effectOfPublication
Indicates the impact or consequence that a particular publication has on something, such as knowledge, behavior, policy, or subsequent events.
-
D.
readerReception
chosen
Indicates how readers interpret, respond to, or are affected by a particular text or work.
-
E.
audienceImpact
Indicates how an action, message, or event affects, influences, or resonates with its intended audience.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cc20c08190a6a678befe1061dd |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:02 p.m.