Triple
T32173103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Hood (Jason Todd) |
E821762
|
entity |
| Predicate | usesLethalForce |
P44969
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Red Hood (Jason Todd), usesLethalForce, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLethalForce Context triple: [Red Hood (Jason Todd), usesLethalForce, true]
-
A.
usesFirearmsUnit
Indicates that one entity employs or operates firearms as part of a specific unit or organizational grouping.
-
B.
typeOfUseOfForce
chosen
Indicates the specific manner or category of force applied in an interaction or incident.
-
C.
usedViolenceFor
Indicates that an entity employed physical force or violent means in order to achieve, enable, or support a particular goal, outcome, or activity.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:33 a.m.