Triple
T4995743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Provincial Council |
E112241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial legislative upper house |
C190
|
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 legislative upper house Context triple: [New Jersey Provincial Council, instanceOf, colonial legislative upper house]
-
A.
colonial legislature
chosen
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.
-
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.
bicameral legislature
A bicameral legislature is a lawmaking body composed of two separate chambers or houses that must typically both approve legislation for it to become law.
-
D.
parliamentary estate system
A parliamentary estate system is a historical form of representative governance in which society is divided into distinct estates or orders (such as clergy, nobility, and commoners), each sending its own delegates to a parliamentary assembly with defined rights and privileges.
-
E.
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.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:34 p.m.