Triple
T4290450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Everest |
E97375
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Surveyor General of India |
C15534
|
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: Surveyor General of India Context triple: [George Everest, instanceOf, Surveyor General of India]
-
A.
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.
-
B.
Governor of Madras
The Governor of Madras was the chief colonial administrator of the Madras Presidency under British rule in India, responsible for overseeing governance, law, and policy implementation in the region.
-
C.
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.
-
D.
secretary to the Government of India
The Secretary to the Government of India is the senior-most civil servant in a ministry or department, responsible for policy formulation, administration, and advising the Minister on all governmental matters within their domain.
-
E.
Secretary of State for India
The Secretary of State for India was the British Cabinet minister responsible for overseeing the administration, governance, and imperial policy of British India from 1858 to 1947.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.