Triple
T25672664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krajina region |
E643719
|
entity |
| Predicate | sawMilitaryOperation |
P72293
|
FINISHED |
| Object | Operation Storm |
—
|
NE NERFINISHED |
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: Operation Storm | Statement: [Krajina region, sawMilitaryOperation, Operation Storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawMilitaryOperation Context triple: [Krajina region, sawMilitaryOperation, Operation Storm]
-
A.
coordinatesMilitaryOperationsOf
Indicates having authority to plan, direct, and manage the military operations carried out by another entity.
-
B.
hadMajorOperationsIn
Indicates that an entity has undergone significant or primary operations or activities in a specified location or context.
-
C.
militaryActivity
Indicates that an entity is engaged in, associated with, or affected by actions, operations, or preparations conducted by armed forces.
-
D.
militaryOperationName
chosen
Indicates the specific named military operation associated with an action, event, or entity.
-
E.
sawCombat
Indicates that an entity directly participated in active military or armed conflict.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3389ac819092997022ed2bc2f8 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:30 p.m.