Triple
T22329408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSA Norway |
E551982
|
entity |
| Predicate | usesRegulatoryApproach |
P75623
|
FINISHED |
| Object | risk-based supervision |
—
|
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: risk-based supervision | Statement: [PSA Norway, usesRegulatoryApproach, risk-based supervision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRegulatoryApproach Context triple: [PSA Norway, usesRegulatoryApproach, risk-based supervision]
-
A.
complianceApproach
chosen
Indicates the method or strategy an entity uses to meet, adhere to, or enforce specified rules, standards, or regulatory requirements.
-
B.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
C.
associatedWithRegulation
Indicates a relationship where something is linked to, governed by, or relevant to a specific regulation or regulatory framework.
-
D.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
-
E.
regulatoryTool
Indicates that something functions as an instrument, mechanism, or means used to establish, enforce, or guide rules, standards, or controls over another entity or process.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576ab52c819087563cd778d6bc5e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.