Triple
T4664946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British East India Company forces |
E102823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European colonial army in Asia |
C12747
|
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: European colonial army in Asia Context triple: [British East India Company forces, instanceOf, European colonial army in Asia]
-
A.
Javanese military campaign
A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or strategic objectives.
-
B.
branch of the British Indian Army
A branch of the British Indian Army is a major organizational subdivision responsible for a specific type of military function or service, such as infantry, cavalry, artillery, or engineering, within the colonial armed forces of British India.
-
C.
British East India Company regiment
chosen
A British East India Company regiment was a military unit raised, organized, and maintained by the Company in India to protect its commercial interests, enforce territorial control, and support colonial governance.
-
D.
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.
-
E.
royal army
A royal army is a formally organized, state-sanctioned military force that serves, protects, and enforces the authority and interests of a monarchy.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.