Triple
T26033760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant of the Islamic Resistance Movement |
E647498
|
entity |
| Predicate | supportsTactic |
P75814
|
FINISHED |
| Object | armed struggle |
—
|
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 struggle | Statement: [Covenant of the Islamic Resistance Movement, supportsTactic, armed struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTactic Context triple: [Covenant of the Islamic Resistance Movement, supportsTactic, armed struggle]
-
A.
tacticOf
Indicates that one entity is a tactic, method, or strategy employed or used by another entity.
-
B.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
D.
hasPrimaryTactic
chosen
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
E.
supportsProsecutionIn
Indicates that an entity provides assistance or backing to the prosecution side within a specified legal case or jurisdiction.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 22, 2026, 9:06 a.m.