Triple
T4943010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Red Spot |
E110981
|
entity |
| Predicate | windSpeed |
P60166
|
FINISHED |
| Object | up to about 430 km/h |
—
|
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: up to about 430 km/h | Statement: [Great Red Spot, windSpeed, up to about 430 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windSpeed Context triple: [Great Red Spot, windSpeed, up to about 430 km/h]
-
A.
windResource
Indicates the availability, quality, or characteristics of wind at a location as a usable energy resource.
-
B.
windResistance
Indicates the degree to which an entity opposes or reduces the effect of wind acting upon it.
-
C.
prevailingSurfaceWinds
Indicates the typical or most frequently occurring wind direction and speed that dominate at a given location over a specified period.
-
D.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
-
E.
windDirectionAtLandfall
Indicates the direction from which the wind is blowing at the moment and location where a storm makes landfall.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff85b50819081d78087caa6b473 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:31 p.m.