Triple
T5299191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Karbala-5 |
E119932
|
entity |
| Predicate | tacticsUsedByIran |
P30685
|
FINISHED |
| Object | human wave attacks |
—
|
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: human wave attacks | Statement: [Operation Karbala-5, tacticsUsedByIran, human wave attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsUsedByIran Context triple: [Operation Karbala-5, tacticsUsedByIran, human wave attacks]
-
A.
PersianTactics
Indicates the use or application of military strategies, maneuvers, or methods characteristic of Persian forces in a conflict or battle context.
-
B.
militaryTacticsUsed
chosen
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
C.
impactOnIran
Indicates the effect or consequences that an action, event, or policy has on Iran.
-
D.
militaryTacticsFaced
Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
-
E.
strategyUsedByRussians
Indicates a strategy or tactic that is employed or implemented by Russians.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.