Triple

T11652288
Position Surface form Disambiguated ID Type / Status
Subject Pakistani rupee E276932 entity
Predicate hasInflationTargeting P14215 FINISHED
Object no 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: no | Statement: [Pakistani rupee, hasInflationTargeting, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInflationTargeting
Context triple: [Pakistani rupee, hasInflationTargeting, no]
  • A. inflationTargetManagedBy
    Indicates that the responsibility for setting, overseeing, or adjusting an inflation target lies with a particular managing authority or entity.
  • B. hasInflationTargetImplicit
    Indicates that an entity maintains an inflation target that is not formally announced or explicitly stated, but is understood or inferred from its behavior or policies.
  • C. inflationTargetCountry chosen
    Indicates that a country has adopted or is subject to a specific inflation target as part of its monetary or economic policy.
  • D. inflationTargetEffectiveFrom
    Indicates the date or time from which a specified inflation target becomes valid and starts to apply.
  • E. monetaryPolicyGoal
    Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a2d01f9c8190849f252f22519550 completed April 10, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69d85ddc780481909a3bc63832fe2bd2 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.