Triple
T578416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaelic Language (Scotland) Act 2005 |
E15007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Act of the Scottish Parliament |
C4111
|
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: Act of the Scottish Parliament Context triple: [Gaelic Language (Scotland) Act 2005, instanceOf, Act of the Scottish Parliament]
-
A.
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.
-
B.
Act of Parliament of England
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.
-
C.
settlement in Scotland
A settlement in Scotland is any inhabited place, ranging from small hamlets and villages to towns and cities, recognized as a distinct community within the country’s geographic and administrative landscape.
-
D.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
-
E.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
- F. None of above. chosen
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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:33 p.m.