Triple
T29755407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Pacific tropical cyclone intensity scale |
E753016
|
entity |
| Predicate | Category1LowerBoundWind |
P168782
|
FINISHED |
| Object | 63 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: 63 km/h | Statement: [South Pacific tropical cyclone intensity scale, Category1LowerBoundWind, 63 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Category1LowerBoundWind Context triple: [South Pacific tropical cyclone intensity scale, Category1LowerBoundWind, 63 km/h]
-
A.
hasWindPressure
Indicates that an entity is subject to or characterized by a specific level or value of wind-induced pressure.
-
B.
category4UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of Category 4 in a classification scale.
-
C.
typicalWindStrength
Indicates the usual or characteristic intensity of wind associated with something, such as a place, time, or condition.
-
D.
category1UpperBound_mph
Indicates the maximum speed limit, in miles per hour, that defines the upper boundary of category 1.
-
E.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 7:56 p.m.