Triple
T3099670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reglamento para el gobierno de la provincia de Californias |
E64684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ordenanza administrativa colonial |
C5062
|
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: ordenanza administrativa colonial Context triple: [Reglamento para el gobierno de la provincia de Californias, instanceOf, ordenanza administrativa colonial]
-
A.
provincial order
chosen
A provincial order is a formal directive or regulation issued by a regional or provincial authority that governs specific activities, behaviors, or administrative procedures within its jurisdiction.
-
B.
colonial policy
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.
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.
-
D.
decree
A decree is an authoritative and formal order or decision issued by a person or body with legal or official power, often carrying the force of law.
-
E.
royal decree
A royal decree is an official, authoritative order or proclamation issued by a monarch that carries the force of law within their realm.
- 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.