Triple
T6656919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Decisive Storm |
E150968
|
entity |
| Predicate | airStrikes |
P72128
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Operation Decisive Storm, airStrikes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airStrikes Context triple: [Operation Decisive Storm, airStrikes, yes]
-
A.
airCommander
Indicates that an entity serves as the commanding officer or leader of air forces or air operations for another entity.
-
B.
airForceInvolved
Indicates that an air force participates in, contributes to, or is otherwise involved in a specified event, operation, or situation.
-
C.
notableAirOperation
Indicates that there is a significant or historically important air operation associated with the subject.
-
D.
airborneForces
Indicates that military forces are deployed, transported, or operating via aircraft, typically inserted from the air into an operational area.
-
E.
opponentAircraft
Indicates that one aircraft is an adversary or opposing aircraft relative to another in a conflict or competitive context.
- F. None of above. chosen
Provenance (4 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.