Triple
T19678219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oenone |
E472510
|
entity |
| Predicate | laterRepented |
P62179
|
FINISHED |
| Object | refusal to heal Paris |
—
|
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: refusal to heal Paris | Statement: [Oenone, laterRepented, refusal to heal Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRepented Context triple: [Oenone, laterRepented, refusal to heal Paris]
-
A.
repentedIn
Indicates that an entity has expressed remorse or regret for its actions within a particular context, time, or situation.
-
B.
repentedTo
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
C.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
D.
laterRegretted
chosen
Indicates that an entity experienced regret at a later time about a prior action, decision, or state involving another entity.
-
E.
soughtPardonFor
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bda8348190b0c7816c50aca923 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.