Triple
T5740282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Vijay (1999) |
E126597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian 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: Indian military operation Context triple: [Operation Vijay (1999), instanceOf, Indian 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.
Indian Army position
An Indian Army position is a specific rank or role within the organizational hierarchy of the Indian Army, defining an individual's authority, responsibilities, and duties in military operations and administration.
-
C.
Indian Army command
Indian Army command is an organizational unit responsible for directing, coordinating, and controlling military operations, administration, and logistics within a defined geographic or functional area of the Indian Army.
-
D.
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.
-
E.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:48 p.m.