Triple
T17307302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of the British East India Company |
E420195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era legal instrument |
C22986
|
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-era legal instrument Context triple: [Treaties of the British East India Company, instanceOf, colonial-era legal instrument]
-
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 governing charter
chosen
A colonial governing charter is a formal legal document issued by a sovereign power that establishes the framework, authority, and rules by which a colony is organized and governed.
-
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 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.
-
E.
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.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.