Triple
T14025884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Python (1971) |
E337454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Navy operation |
C33973
|
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 Navy operation Context triple: [Operation Python (1971), instanceOf, Indian Navy operation]
-
A.
Indian Navy sailor
An Indian Navy sailor is an enlisted maritime professional who operates, maintains, and supports naval ships, submarines, and aircraft to safeguard India’s maritime interests and national security.
-
B.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
-
C.
formation of the Indian Navy
The formation of the Indian Navy refers to the historical evolution and establishment of India’s maritime armed force from colonial-era naval units into an independent, sovereign navy responsible for safeguarding the nation’s maritime interests.
-
D.
Indian naval air station
An Indian naval air station is a shore-based military aviation facility of the Indian Navy that supports, operates, and maintains naval aircraft for maritime defense, surveillance, and related operations.
-
E.
U.S. Navy operation
A U.S. Navy operation is a coordinated maritime, air, cyber, and/or land activity conducted by the United States Navy to achieve specific military, security, or humanitarian objectives under defined rules of engagement and command structures.
- F. None of above. chosen
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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.