Triple
T3099671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reglamento para el gobierno de la provincia de Californias |
E64684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reglamento colonial español |
C1297
|
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: reglamento colonial español Context triple: [Reglamento para el gobierno de la provincia de Californias, instanceOf, reglamento colonial español]
-
A.
Spanish colonial settlement
A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
-
B.
colonial policy
chosen
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
-
C.
Spanish colonial institution
A Spanish colonial institution is an organization or system established by the Spanish Empire to administer, control, and exploit its overseas territories through political, economic, religious, and social structures.
-
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.
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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.