Triple
T310754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | satisfaction theory of atonement |
E7601
|
entity |
| Predicate | holdsThat |
P6511
|
FINISHED |
| Object | human sin offends the honor of God |
—
|
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: human sin offends the honor of God | Statement: [satisfaction theory of atonement, holdsThat, human sin offends the honor of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsThat Context triple: [satisfaction theory of atonement, holdsThat, human sin offends the honor of God]
-
A.
heldThat
chosen
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
-
B.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
C.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
D.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
E.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.