Triple
T23539589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anil Yashwant Tipnis |
E577701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Air Force officer |
C47794
|
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 Air Force officer Context triple: [Anil Yashwant Tipnis, instanceOf, Indian Air Force officer]
-
A.
Royal Australian Air Force officer
A Royal Australian Air Force officer is a commissioned member of Australia's air and space warfare branch responsible for leading personnel, managing operations, and upholding the defense and strategic interests of the nation.
-
B.
Indian Air Force unit
An Indian Air Force unit is an organized formation of personnel, aircraft, and support resources structured to conduct specific air and space operations, training, or support functions within the Indian Air Force.
-
C.
Peruvian Air Force officer
A Peruvian Air Force officer is a commissioned member of Peru’s military aviation branch responsible for leading personnel, planning and executing air operations, and safeguarding the country’s airspace and national security interests.
-
D.
Royal Flying Corps officer
A Royal Flying Corps officer is a commissioned member of the British Army’s pre-RAF air arm (1912–1918), responsible for leading, flying, and managing aerial operations, personnel, and equipment during the early development of military aviation.
-
E.
United States Air Force airman
A United States Air Force airman is an enlisted or commissioned member of the U.S. Air Force responsible for supporting and executing air, space, and cyberspace operations in defense of national security.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:10 p.m.