Triple
T7696620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Thailand |
E174385
|
entity |
| Predicate | setsPolicyRate |
P78337
|
FINISHED |
| Object | BOT policy 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: BOT policy rate | Statement: [Bank of Thailand, setsPolicyRate, BOT policy rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsPolicyRate Context triple: [Bank of Thailand, setsPolicyRate, BOT policy rate]
-
A.
usesPolicyRate
Indicates that one entity applies or bases its actions or decisions on a specified policy interest rate.
-
B.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
C.
settlementPolicy
Indicates the rules or arrangements governing how and when obligations, transactions, or disputes between parties are finalized and settled.
-
D.
rechargeRate
Indicates the rate or speed at which something restores or replenishes its capacity, energy, or resources over time.
-
E.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
- F. None of above. chosen
Provenance (4 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.