Triple
T283576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Data-processing and Forecasting System |
E5839
|
entity |
| Predicate | supportsTimescale |
P9092
|
FINISHED |
| Object | nowcasting |
—
|
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: nowcasting | Statement: [Global Data-processing and Forecasting System, supportsTimescale, nowcasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimescale Context triple: [Global Data-processing and Forecasting System, supportsTimescale, nowcasting]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0d789881908d6a9a8d6a0d4a6c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.