Triple
T15041564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Code of Judicial Procedure |
E378611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of law in Sweden |
C34701
|
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: source of law in Sweden Context triple: [Swedish Code of Judicial Procedure, instanceOf, source of law in Sweden]
-
A.
Swedish law
Swedish law is the body of legal rules and principles governing Sweden, encompassing its constitution, legislation, case law, and administrative regulations that regulate public and private life within the country.
-
B.
Estonian law
Estonian law is the body of legal rules and principles governing the Republic of Estonia, based on a civil law system, the Constitution, and legislation enacted by the Riigikogu, supplemented by EU law and international agreements.
-
C.
Norwegian statute
A Norwegian statute is a formal written law enacted by the Norwegian Parliament (Storting) that establishes binding legal rules within Norway’s jurisdiction.
-
D.
source of international law
A source of international law is any recognized method or process—such as treaties, customary practice, general principles, judicial decisions, and scholarly writings—through which binding legal rules governing relations between states and other international actors are created or identified.
-
E.
source of constitutional law
A source of constitutional law is any authoritative origin—such as a written constitution, judicial decisions, conventions, or scholarly writings—from which the fundamental rules and principles governing a state’s constitutional order are derived.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.