Triple
T30145938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Courts of Ceylon |
E766253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial court system |
C768
|
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 court system Context triple: [District Courts of Ceylon, instanceOf, colonial court system]
-
A.
colonial legal system
A colonial legal system is a framework of laws, courts, and enforcement mechanisms imposed by a colonizing power to govern a colonized territory, typically prioritizing imperial interests and often subordinating or reshaping indigenous legal traditions.
-
B.
colonial tribunal
chosen
A colonial tribunal is a judicial body established by a colonial power to administer law, resolve disputes, and enforce imperial authority within a colonized territory.
-
C.
colonial legal case
A colonial legal case is a formal dispute or prosecution adjudicated within a legal system established by a colonial power over a subject territory, reflecting the laws, institutions, and power dynamics of colonial rule.
-
D.
colonial law code
A colonial law code is a formalized set of legal rules and procedures imposed by a colonial power to govern its territories and subjects, often blending metropolitan laws with local customs to maintain control and order.
-
E.
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.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:18 p.m.