Triple
T1409770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reserve Bank of India |
E31776
|
entity |
| Predicate | setsPolicyInstrument |
P1652
|
FINISHED |
| Object | repo rate |
—
|
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: repo rate | Statement: [Reserve Bank of India, setsPolicyInstrument, repo rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsPolicyInstrument Context triple: [Reserve Bank of India, setsPolicyInstrument, repo rate]
-
A.
policyTool
chosen
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
B.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
C.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
D.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
E.
authorizationInstrument
Indicates that one entity serves as the formal legal or official instrument that grants authority or permission for another entity or action.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e0bfd08190a50820bc7585c28f |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.