Triple
T786340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian krone |
E16810
|
entity |
| Predicate | inflationTargeting |
P14215
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Norwegian krone, inflationTargeting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inflationTargeting Context triple: [Norwegian krone, inflationTargeting, yes]
-
A.
inflationTargetManagedBy
Indicates that the responsibility for setting, overseeing, or adjusting an inflation target lies with a particular managing authority or entity.
-
B.
inflationTargetCountry
chosen
Indicates that a country has adopted or is subject to a specific inflation target as part of its monetary or economic policy.
-
C.
monetaryPolicyGoal
Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
-
D.
monetaryPolicyTool
Indicates that something functions as an instrument or mechanism used to implement or influence a government's or central bank's monetary policy.
-
E.
monetaryPolicyRegime
Indicates the type and rules of a central bank’s approach to managing money supply, interest rates, and inflation in an economy.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.