Triple
T23175586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Education Service |
E578991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial civil service |
C2533
|
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 civil service Context triple: [Indian Education Service, instanceOf, colonial civil service]
-
A.
colonial administrative service
chosen
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.
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.
-
D.
colonial institutions
Colonial institutions are the formal and informal political, legal, economic, and social structures established by colonial powers to govern, extract resources from, and control colonized populations, often leaving long-lasting impacts on postcolonial societies.
-
E.
instrument of colonial administration
An instrument of colonial administration is any institutional mechanism, policy, or practice deliberately used by a colonial power to govern, control, and extract resources from colonized populations and territories.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:04 p.m.