Triple
T4341535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British India Command |
E97791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military formation |
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: British military formation Context triple: [British India Command, instanceOf, British military formation]
-
A.
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.
-
B.
Australian Army formation
An Australian Army formation is a structured military organization composed of multiple units and sub-units, established to plan, coordinate, and conduct land operations under a unified command within the Australian Army.
-
C.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
D.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
-
E.
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.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:14 p.m.