Triple
T5935408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise Chamber of the Amsterdam Court of Appeal |
E132030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch judicial body |
C6641
|
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: Dutch judicial body Context triple: [Enterprise Chamber of the Amsterdam Court of Appeal, instanceOf, Dutch judicial body]
-
A.
Dutch public body
A Dutch public body is an organization established by or under Dutch public law, entrusted with performing public tasks or exercising public authority under government oversight.
-
B.
government body of the Kingdom of the Netherlands
A government body of the Kingdom of the Netherlands is an official public institution or authority, established by law, that exercises administrative, legislative, or judicial powers on behalf of the Dutch state or its constituent parts.
-
C.
Dutch statute
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.
-
D.
Judicial body
chosen
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
E.
Belgian federal government
The Belgian federal government is the central governing authority of Belgium, responsible for national policy areas such as defense, justice, social security, and federal finance, operating within a complex federal system that shares powers with regional and community governments.
- 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.