Triple
T2145140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Indian Division |
E47047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formation of the British Indian Army |
C1740
|
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: formation of the British Indian Army Context triple: [4th Indian Division, instanceOf, formation of the British Indian Army]
-
A.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
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.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
D.
British Army organizational element
chosen
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.
-
E.
World War II military formation
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.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:44 p.m.