Triple
T16742041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal instructions |
E406856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial governance document |
C27413
|
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 governance document Context triple: [Royal instructions, instanceOf, colonial governance document]
-
A.
colonial governing charter
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.
-
B.
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.
-
C.
colonial political organization
A colonial political organization is a governing structure imposed by a foreign power to administer, control, and exploit a colonized territory and its population, often subordinating local institutions and interests to imperial objectives.
-
D.
colonial legislature
A colonial legislature is a representative governing body established in a colony to create laws, manage local affairs, and advise or balance the authority of the colonial governor and imperial power.
-
E.
historical political document
chosen
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.