Triple
T25677986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Army (for parts around Fort William) |
E643858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional formation of the Indian Army |
C14943
|
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: regional formation of the Indian Army Context triple: [Indian Army (for parts around Fort William), instanceOf, regional formation of the Indian Army]
-
A.
Indian Army formation
chosen
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.
-
B.
Indian Armed Forces formation
An Indian Armed Forces formation is an organized military unit or grouping, such as a command, corps, division, brigade, or equivalent structure, established to plan, coordinate, and conduct operations within the Indian Army, Navy, or Air Force.
-
C.
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.
-
D.
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.
-
E.
branch of the Indian Army
A branch of the Indian Army is a major organizational subdivision responsible for specific operational, combat, or support functions within the Army’s overall structure.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 7:42 p.m.