Triple
T832645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Self-Denying Ordinance |
E17999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English Civil War legislation |
C2432
|
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: English Civil War legislation Context triple: [Self-Denying Ordinance, instanceOf, English Civil War legislation]
-
A.
Act of Parliament of England
chosen
An Act of Parliament of England is a formal written law enacted by the English Parliament prior to the 1707 Acts of Union, having legal force within the Kingdom of England and its territories.
-
B.
Act of Parliament of the United Kingdom
An Act of Parliament of the United Kingdom is a formal law enacted by the UK Parliament, comprising the House of Commons, the House of Lords, and the monarch, which has legal force throughout its applicable jurisdictions.
-
C.
session of the Parliament of England
A session of the Parliament of England is a formally convened period during which the English Parliament meets to debate, legislate, and conduct governmental and political business before being prorogued or dissolved.
-
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.
Puritan controversy
A Puritan controversy is a historical or theological dispute arising within Puritan communities over matters of doctrine, church governance, or moral practice that challenged established religious authority and norms.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.