Triple
T36642511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenSTEF |
E904619
|
entity |
| Predicate | supportsTimeHorizon |
P9092
|
FINISHED |
| Object | intra-day forecasting |
—
|
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: intra-day forecasting | Statement: [OpenSTEF, supportsTimeHorizon, intra-day forecasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimeHorizon Context triple: [OpenSTEF, supportsTimeHorizon, intra-day forecasting]
-
A.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
B.
supportsTimescale
chosen
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
C.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
D.
supportsTimeDistribution
Indicates that one entity provides or enables the allocation, scheduling, or distribution of time-related resources or events for another entity.
-
E.
hasHorizon
Indicates that an entity possesses or is characterized by a visible boundary line where its surface or extent appears to meet the sky or a distant limit.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.