Triple
T34853998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bathinda Cantonment |
E1004677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Army cantonment |
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 cantonment Context triple: [Bathinda Cantonment, instanceOf, Indian Army cantonment]
-
A.
Indian Army station
chosen
An Indian Army station is a permanent or semi-permanent military establishment where Indian Army units are based, trained, housed, and supported with necessary administrative and logistical infrastructure.
-
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 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.
-
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.
administrative division of the Indian Army
An administrative division of the Indian Army is a territorial or functional organizational unit responsible for managing personnel, logistics, training, and support services within its designated area or scope.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.