Triple
T33714496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprus Constitution of 1882 |
E863831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial legal framework |
C32000
|
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 legal framework Context triple: [Cyprus Constitution of 1882, instanceOf, colonial legal framework]
-
A.
colonial legal system
chosen
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 legal position
A colonial legal position is a formally defined status within a colonial legal system that determines an individual’s rights, obligations, and access to legal protections under imperial rule.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.