Triple
T7873062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaza–Israel conflict (post-2005 phase) |
E182784
|
entity |
| Predicate | involvesTactic |
P59465
|
FINISHED |
| Object | indiscriminate rocket fire |
—
|
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: indiscriminate rocket fire | Statement: [Gaza–Israel conflict (post-2005 phase), involvesTactic, indiscriminate rocket fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTactic Context triple: [Gaza–Israel conflict (post-2005 phase), involvesTactic, indiscriminate rocket fire]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
hasPrimaryTactic
Indicates that an entity is associated with its main or most commonly used tactic or method of operation.
-
C.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
D.
involvedAction
chosen
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
E.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a6d93881908d68386e49bea1e3 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:56 p.m.