Triple
T1405913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algerian War of Independence |
E31690
|
entity |
| Predicate | involvedTactic |
P1716
|
FINISHED |
| Object | guerrilla warfare |
—
|
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: guerrilla warfare | Statement: [Algerian War of Independence, involvedTactic, guerrilla warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedTactic Context triple: [Algerian War of Independence, involvedTactic, guerrilla warfare]
-
A.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
hasCommonTacticOfActivists
Indicates that multiple activists share or employ the same tactic in their activities or campaigns.
-
C.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.