Triple
T10590953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | killing of Sitting Bull |
E249984
|
entity |
| Predicate | hasTypeOfForceUsed |
P44969
|
FINISHED |
| Object | armed arrest attempt |
—
|
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: armed arrest attempt | Statement: [killing of Sitting Bull, hasTypeOfForceUsed, armed arrest attempt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfForceUsed Context triple: [killing of Sitting Bull, hasTypeOfForceUsed, armed arrest attempt]
-
A.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
B.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
C.
typeOfUseOfForce
chosen
Indicates the specific manner or category of force applied in an interaction or incident.
-
D.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
-
E.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277b66448190b668c47fe6af4f3d |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.