Triple
T9796769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbert Saffir |
E237735
|
entity |
| Predicate | scaleCategories |
P90024
|
FINISHED |
| Object | Category 1 hurricanes |
—
|
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: Category 1 hurricanes | Statement: [Herbert Saffir, scaleCategories, Category 1 hurricanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleCategories Context triple: [Herbert Saffir, scaleCategories, Category 1 hurricanes]
-
A.
mapScaleCategory
Indicates the classification of a map based on its scale range or level of detail.
-
B.
seriesScale
Indicates that one value or measurement is expressed relative to another according to a defined proportional scale within a series.
-
C.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
D.
scalingProperty
Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
-
E.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34a53548190a8cb524381fe2bf9 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:28 p.m.