Triple
T33265098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borachio |
E851621
|
entity |
| Predicate | expressesRemorseFor |
P125251
|
FINISHED |
| Object | slandering Hero |
—
|
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: slandering Hero | Statement: [Borachio, expressesRemorseFor, slandering Hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressesRemorseFor Context triple: [Borachio, expressesRemorseFor, slandering Hero]
-
A.
repentsFor
chosen
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
B.
repentedIn
Indicates that an entity has expressed remorse or regret for its actions within a particular context, time, or situation.
-
C.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
D.
repentedTo
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
E.
penance
Indicates an act of self-imposed suffering, discipline, or reparation performed to atone for a wrongdoing or moral failing.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:32 a.m.