Triple
T4326990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank Rate |
E96655
|
entity |
| Predicate | timeHorizonOfImpact |
P56262
|
FINISHED |
| Object | short to 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: short to medium term | Statement: [Bank Rate, timeHorizonOfImpact, short to medium term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeHorizonOfImpact Context triple: [Bank Rate, timeHorizonOfImpact, short to medium term]
-
A.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
B.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
C.
impactCategory
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
D.
impactIfCompleted
Indicates the effect or consequence that will occur if the referenced task or action is fully completed.
-
E.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35131f11881909e2d5415a70d5785 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:13 p.m.