Triple
T22386770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Petroleum Regulations |
E553415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian regulation |
C17961
|
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: Norwegian regulation Context triple: [Norwegian Petroleum Regulations, instanceOf, Norwegian regulation]
-
A.
Norwegian statute
chosen
A Norwegian statute is a formal written law enacted by the Norwegian Parliament (Storting) that establishes binding legal rules within Norway’s jurisdiction.
-
B.
Norwegian court
A Norwegian court is a judicial body within Norway’s legal system responsible for interpreting and applying the law, resolving disputes, and safeguarding legal rights through formal proceedings.
-
C.
Norwegian foundation
A Norwegian foundation is a legally independent, non-profit entity in Norway that manages assets dedicated to specific public-benefit, charitable, cultural, or private purposes according to a founding document and national regulations.
-
D.
Danish law
Danish law is the national legal system of Denmark, based on a civil law tradition with strong welfare-state principles, comprehensive statutory regulation, and adherence to international and EU legal obligations.
-
E.
Norwegian organization
A Norwegian organization is an entity based in Norway, such as a company, association, or institution, that is formally structured to pursue specific economic, social, cultural, or public objectives under Norwegian law.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.