Triple

T246930
Position Surface form Disambiguated ID Type / Status
Subject Indian rupee E5057 entity
Predicate inflationTargetBand P5393 FINISHED
Object 2% to 6% 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: 2% to 6% | Statement: [Indian rupee, inflationTargetBand, 2% to 6%]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inflationTargetBand
Context triple: [Indian rupee, inflationTargetBand, 2% to 6%]
  • A. inflationTargetManagedBy
    Indicates that the responsibility for setting, overseeing, or adjusting an inflation target lies with a particular managing authority or entity.
  • B. monetaryPolicyGoal chosen
    Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
  • C. monetaryPolicyRegime
    Indicates the type and rules of a central bank’s approach to managing money supply, interest rates, and inflation in an economy.
  • 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. centralBank
    Indicates that an entity functions as the primary monetary authority responsible for issuing currency and implementing monetary policy for a specific jurisdiction.
  • 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_69a257c4bf688190a46ebbf411ab7473 completed Feb. 28, 2026, 2:49 a.m.
NER Named-entity recognition batch_69a25d13b8088190a3f48f0388d57496 completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b63b0bc8190864d7324d339fb48 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:54 a.m.