Triple
T5138068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Grace |
E115875
|
entity |
| Predicate | encouragesResponse |
P836
|
FINISHED |
| Object | repentance |
—
|
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: repentance | Statement: [Sovereign Grace, encouragesResponse, repentance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encouragesResponse Context triple: [Sovereign Grace, encouragesResponse, repentance]
-
A.
encourages
chosen
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
B.
settlementEncouragedBy
Indicates that the establishment or growth of a settlement is promoted, supported, or stimulated by a particular factor, agent, or condition.
-
C.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
D.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
E.
encouragedDoctrine
Indicates that an entity actively promoted or urged others to adopt or follow a particular doctrine or set of beliefs.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.