Triple
T25254255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monetary Policy Committee (South African Reserve Bank) |
E633123
|
entity |
| Predicate | timeHorizonForPolicy |
P38657
|
FINISHED |
| Object | medium term |
—
|
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: medium term | Statement: [Monetary Policy Committee (South African Reserve Bank), timeHorizonForPolicy, medium term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeHorizonForPolicy Context triple: [Monetary Policy Committee (South African Reserve Bank), timeHorizonForPolicy, medium term]
-
A.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
B.
goalHorizon
chosen
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
C.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
D.
predictionHorizon
Indicates the temporal extent into the future over which a prediction or forecast is intended to apply.
-
E.
planningHorizonYears
Indicates the number of years into the future over which planning or forecasting is intended to be carried out.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808e7b288190ad7444ccbef04d80 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:12 p.m.