Triple
T23681702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwalior Cantonment |
E585040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Army station |
C47950
|
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 Army station Context triple: [Gwalior Cantonment, instanceOf, Indian Army station]
-
A.
Indian Air Force station
An Indian Air Force station is a permanent military airbase facility operated by the Indian Air Force that supports aircraft operations, training, logistics, and administrative functions for air defense and related missions.
-
B.
Indian Army institution
An Indian Army institution is an official military establishment or organization under the Indian Army that provides training, education, research, administration, or support functions to enhance the army’s operational effectiveness and professional development.
-
C.
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.
-
D.
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.
-
E.
Indian Army formation
An Indian Army formation is an organized military unit or grouping, such as a corps, division, brigade, or battalion, structured for command, control, and execution of land-based operations within the Indian Army.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.