Triple

T22380557
Position Surface form Disambiguated ID Type / Status
Subject United States monetary system E553260 entity
Predicate monetaryPolicyGoals P5393 FINISHED
Object price stability 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: price stability | Statement: [United States monetary system, monetaryPolicyGoals, price stability]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: monetaryPolicyGoals
Context triple: [United States monetary system, monetaryPolicyGoals, price stability]
  • A. monetaryPolicyGoal chosen
    Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
  • B. monetaryPolicyTool
    Indicates that something functions as an instrument or mechanism used to implement or influence a government's or central bank's monetary policy.
  • C. hasMonetaryPolicy
    Indicates that one entity defines, controls, or is responsible for the monetary policy applied to another entity (such as a country, region, or currency area).
  • D. monetaryPolicyInput
    Indicates that an entity provides information, data, or influence used in forming or adjusting monetary policy decisions.
  • E. monetaryPolicyContext
    Indicates the economic and institutional setting within which monetary policy decisions are formulated, communicated, and implemented.
  • 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1582c05fc8190836ae008426177a5 completed April 29, 2026, 1 a.m.
PD Predicate disambiguation batch_69e73011e6388190a05edf137f488441 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:45 p.m.