Triple
T21482094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Jones |
E530017
|
entity |
| Predicate | seeksForgivenessFrom |
P75734
|
FINISHED |
| Object | former colleagues |
—
|
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: former colleagues | Statement: [Adam Jones, seeksForgivenessFrom, former colleagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksForgivenessFrom Context triple: [Adam Jones, seeksForgivenessFrom, former colleagues]
-
A.
soughtPardonFor
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
-
B.
demandedAtonementFrom
Indicates that one entity required another to make amends or provide compensation for a perceived wrong or offense.
-
C.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
D.
believesHeIsForgivenFor
Indicates that one entity holds the conviction that he has been forgiven by another entity for some wrongdoing or offense.
-
E.
repentedTo
chosen
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea34c4388190adc78d209d2aafb8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.