Triple
T9294659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Olive Branch |
E223609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkish military operation |
C340
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Turkish military operation Context triple: [Operation Olive Branch, instanceOf, Turkish military operation]
-
A.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
B.
Islamic military campaign
An Islamic military campaign is an organized, often state-sanctioned, armed expedition undertaken by Muslim forces to expand, defend, or consolidate territories, influence, or religious-political objectives within an Islamic historical or ideological framework.
-
C.
military operation outcome
A military operation outcome is the overall result or consequence of a planned military action, encompassing its achieved objectives, strategic impact, and associated costs or losses.
-
D.
Greco-Turkish War
The Greco-Turkish War is a historical military conflict between Greece and Turkey (or their predecessor states), typically referring to one of several wars from the late 19th to early 20th centuries, most notably the 1919–1922 campaign that concluded with the Turkish War of Independence and the population exchange between the two nations.
-
E.
military intervention
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
- F. None of above.
Provenance (1 batch)
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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:35 p.m.