Triple
T5041686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Military Administration in Malaya |
E113559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial administration |
C10548
|
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 administration Context triple: [British Military Administration in Malaya, instanceOf, British colonial administration]
-
A.
British colonial position
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.
British military administration
chosen
British military administration is the system of governance and organizational structures through which the British armed forces planned, directed, and controlled military operations and occupied territories.
-
D.
presidency of British India
The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
-
E.
British colonial law
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.