Triple
T11989690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Bank of Trinidad and Tobago |
E285372
|
entity |
| Predicate | policyRateName |
P35674
|
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: [Central Bank of Trinidad and Tobago, policyRateName, repo rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyRateName Context triple: [Central Bank of Trinidad and Tobago, policyRateName, repo rate]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
setsPolicyRate
Indicates that an entity determines and establishes the official policy interest rate applied within a monetary or regulatory framework.
-
C.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
-
D.
interestRateName
chosen
Indicates the specific label or designation used to identify a particular interest rate.
-
E.
baseRate
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903afe4388190a2cf2328e85adf9b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.