Triple
T11248692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian law |
E266272
|
entity |
| Predicate | legislationForm |
P2588
|
FINISHED |
| Object | acts of Parliament |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: acts of Parliament | Statement: [Norwegian law, legislationForm, acts of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislationForm Context triple: [Norwegian law, legislationForm, acts of Parliament]
-
A.
signedLegislation
Indicates that an authority formally approved and enacted a piece of legislation into law by signing it.
-
B.
governmentFormProposed
Indicates that a particular form or structure of government has been put forward as a proposal by an entity.
-
C.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
areaOfLegislation
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
E.
enablingLegislationFor
Indicates that one piece of legislation provides the legal authority, framework, or permission necessary for another law, program, or action to exist or operate.
- F. None of above.
Provenance (3 batches)
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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91d1484819098ee6b2efb5316a5 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.