Triple
T32891512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabella |
E841343
|
entity |
| Predicate | asksForMercyFor |
P113203
|
FINISHED |
| Object | Claudio |
—
|
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: Claudio | Statement: [Isabella, asksForMercyFor, Claudio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asksForMercyFor Context triple: [Isabella, asksForMercyFor, Claudio]
-
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.
demandedAtonementFrom
Indicates that one entity required another to make amends or provide compensation for a perceived wrong or offense.
-
C.
mercyRule
Indicates that a game is ended early because one side has achieved a lead so large that continuing is deemed unnecessary or unsporting.
-
D.
scopeOfMercy
Indicates the extent or boundaries within which mercy, leniency, or compassionate treatment is applied in a given context.
-
E.
surrenderDemandedBy
Indicates that one party has demanded the surrender or capitulation of another party.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:18 a.m.