Triple
T8140810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Old Woman |
E190090
|
entity |
| Predicate | suffers |
P46473
|
FINISHED |
| Object | loss of her buttock to soldiers |
—
|
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: loss of her buttock to soldiers | Statement: [the Old Woman, suffers, loss of her buttock to soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffers Context triple: [the Old Woman, suffers, loss of her buttock to soldiers]
-
A.
regardsSufferingAs
Indicates how an entity perceives, evaluates, or emotionally responds to the suffering of another entity.
-
B.
endures
chosen
Indicates that an entity continues to exist, persist, or remain in a particular state or condition over a period of time, often despite challenges or changes.
-
C.
sued
Indicates that one party has initiated legal action or filed a lawsuit against another party in a court of law.
-
D.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
E.
grievesFor
Indicates that one entity feels grief or sorrow because of the loss, suffering, or misfortune of 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4442299881909db56f7475cbb99a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.