Triple
T10272514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governor of Detroit |
E240872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial government position |
C10373
|
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 colonial government position Context triple: [Lieutenant Governor of Detroit, instanceOf, British colonial government position]
-
A.
British colonial position
chosen
A British colonial position is an official role or office established by the British Empire to administer, govern, or oversee territories and populations under colonial rule.
-
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.
United Kingdom government position
A United Kingdom government position is an official role within the UK's system of governance, held by an individual responsible for exercising specific public powers, duties, or administrative functions on behalf of the state.
-
D.
British Indian administrative body
A British Indian administrative body is a colonial-era governing institution established by the British in India to manage political, legal, and economic affairs on behalf of the imperial government.
-
E.
British colonial federation
A British colonial federation is a proposed or actual political union that grouped multiple British colonies under a single federal structure to centralize governance while retaining local administrations.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:36 a.m.