Triple
T33479558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke |
E857431
|
entity |
| Predicate | causeOfGuilt |
P191113
|
FINISHED |
| Object | failure to intervene during a robbery |
—
|
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: failure to intervene during a robbery | Statement: [Luke, causeOfGuilt, failure to intervene during a robbery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfGuilt Context triple: [Luke, causeOfGuilt, failure to intervene during a robbery]
-
A.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
-
B.
revealsGuiltOf
Indicates that one entity exposes or makes evident the guilt or culpability of another entity.
-
C.
actualGuilt
Indicates that an entity truly committed the offense or wrongdoing in question, regardless of legal judgment or perception.
-
D.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
E.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
- F. None of above. chosen
Provenance (4 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 1, 2026, 1:38 a.m.