Triple
T30361700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeanie Deans |
E772304
|
entity |
| Predicate | seeksPardonFor |
P113203
|
FINISHED |
| Object | Effie Deans |
—
|
NE NERFINISHED |
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: Effie Deans | Statement: [Jeanie Deans, seeksPardonFor, Effie Deans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksPardonFor Context triple: [Jeanie Deans, seeksPardonFor, Effie Deans]
-
A.
soughtPardonFor
chosen
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
-
B.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
C.
demandedAtonementFrom
Indicates that one entity required another to make amends or provide compensation for a perceived wrong or offense.
-
D.
apologyIssued
Indicates that one entity has expressed regret or remorse to another entity for a perceived wrong, mistake, or offense.
-
E.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68243b5d8819092d8a0a1261f5fb2 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.