Triple
T2365049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penance |
E47360
|
entity |
| Predicate | contritionType |
P38261
|
FINISHED |
| Object | perfect contrition |
—
|
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: perfect contrition | Statement: [Penance, contritionType, perfect contrition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contritionType Context triple: [Penance, contritionType, perfect contrition]
-
A.
confession
Indicates that one entity admits or discloses information, typically acknowledging guilt, responsibility, or a hidden truth, to another entity.
-
B.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
C.
usesConfession
Indicates that one entity employs or relies on a confession (typically an admission of guilt or wrongdoing) as part of its actions or reasoning toward another entity or outcome.
-
D.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
E.
condemnation
Indicates that an entity expresses strong disapproval or denunciation of another entity, action, or situation.
- F. None of above. chosen
Provenance (4 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc7486cb48190acef1891cc87bdb1 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6a85e2c8190afec217ff29476be |
completed | March 7, 2026, 6:33 a.m. |
Created at: March 4, 2026, 7:55 p.m.