Triple
T5935455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Organization Act of the Netherlands |
E132031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Act of Parliament of the Netherlands |
C14106
|
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 Parliament of the Netherlands Context triple: [Judiciary Organization Act of the Netherlands, instanceOf, Act of Parliament of the Netherlands]
-
A.
Dutch statute
chosen
A Dutch statute is a formal written law enacted by the Dutch legislature (Staten-Generaal) and, where required, sanctioned and promulgated by the government, forming part of the binding legal framework of the Netherlands.
-
B.
Act of Parliament of New Zealand
An Act of Parliament of New Zealand is a law formally enacted by the New Zealand Parliament that establishes, amends, or repeals legal rules within the country’s jurisdiction.
-
C.
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.
-
D.
Dutch state occasion
A Dutch state occasion is a formal, ceremonial event organized or hosted by the Kingdom of the Netherlands to mark significant national, diplomatic, or royal milestones.
-
E.
Act of the Parliament of Scotland
An Act of the Parliament of Scotland is a formal law or statute enacted by the pre-1707 Scottish legislature to regulate legal, political, social, or economic matters within the Kingdom of Scotland.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.