Triple
T7147282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hector Munro |
E166600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British East India Company officer |
C21445
|
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 East India Company officer Context triple: [Hector Munro, instanceOf, British East India Company officer]
-
A.
British East India Company regiment
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.
-
B.
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.
-
C.
British military office
A British military office is an administrative and command center within the United Kingdom’s armed forces where military personnel coordinate operations, manage logistics, and handle official defense-related documentation and communications.
-
D.
Mughal official
A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
-
E.
Governor-General of Bengal
The Governor-General of Bengal was the chief British official in colonial Bengal, later evolving into the de facto head of British administration in India, responsible for overseeing governance, revenue, and foreign affairs in the region.
- F. None of above. chosen
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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.