Triple
T1962794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Madras Army |
E42624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial administrative position |
C4090
|
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: colonial administrative position Context triple: [Commander-in-Chief, Madras Army, instanceOf, colonial administrative position]
-
A.
colonial administrative service
A colonial administrative service is a bureaucratic organization established by a colonial power to govern, manage, and implement policies in its overseas territories.
-
B.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
C.
British colonial administrator
A British colonial administrator is an official appointed by the British government to govern, manage, and implement imperial policies in overseas colonies, overseeing local administration, law, and economic exploitation.
-
D.
public administration position
chosen
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
E.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.