Triple
T19941003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PunishmentsFromGods |
E479305
|
entity |
| Predicate | canBeReversedBy |
P96178
|
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: [PunishmentsFromGods, canBeReversedBy, repentance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeReversedBy Context triple: [PunishmentsFromGods, canBeReversedBy, repentance]
-
A.
canRevertTo
chosen
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
B.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
D.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
E.
alsoReveres
Indicates that one entity holds reverence or deep respect for something or someone that another entity also reveres.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.