Triple
T756941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chindits |
E15577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Indian Army formation |
C2904
|
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: British Indian Army formation Context triple: [Chindits, instanceOf, British Indian Army formation]
-
A.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
B.
presidency of British India
The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
-
C.
World War II military formation
chosen
A World War II military formation is an organized grouping of military units—such as divisions, corps, or armies—structured and deployed by a nation’s armed forces during the Second World War to conduct coordinated combat and support operations.
-
D.
All India Service
All India Service is a category of elite civil services in India whose officers are recruited centrally but serve under both the central and state governments, holding key administrative, policing, and forestry positions across the country.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.