Triple
T3462706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batukeshwar Dutt |
E73062
|
entity |
| Predicate | methodOfStruggle |
P35675
|
FINISHED |
| Object | revolutionary violence |
—
|
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: revolutionary violence | Statement: [Batukeshwar Dutt, methodOfStruggle, revolutionary violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfStruggle Context triple: [Batukeshwar Dutt, methodOfStruggle, revolutionary violence]
-
A.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
B.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
C.
armedStruggleCombinedWith
Indicates a relationship where an armed struggle is carried out in conjunction with another method, strategy, or form of action as part of a combined approach.
-
D.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
E.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.