Triple
T29755415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Pacific tropical cyclone intensity scale |
E753016
|
entity |
| Predicate | Category5LowerBoundWind |
P171570
|
FINISHED |
| Object | 200 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: 200 km/h | Statement: [South Pacific tropical cyclone intensity scale, Category5LowerBoundWind, 200 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Category5LowerBoundWind Context triple: [South Pacific tropical cyclone intensity scale, Category5LowerBoundWind, 200 km/h]
-
A.
Category1LowerBoundWind
Indicates the minimum wind value that defines the lower bound for Category 1 in a classification or scale.
-
B.
Category4LowerBoundWind
Indicates the minimum wind speed threshold at which a storm is classified as Category 4.
-
C.
Category3LowerBoundWind
Indicates the minimum wind speed threshold at which conditions qualify as Category 3 intensity.
-
D.
Category2LowerBoundWind
Indicates that the wind speed meets or exceeds the minimum threshold defined for Category 2 intensity.
-
E.
Category3UpperBoundWind
Indicates the maximum wind speed threshold that defines the upper limit of Category 3 conditions in a wind intensity scale.
- 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_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 28, 2026, 7:56 p.m.