Triple
T8845197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSMC Honolulu |
E210486
|
entity |
| Predicate | typeOfWarningCenter |
P11544
|
FINISHED |
| Object | tropical cyclone warning center |
—
|
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: tropical cyclone warning center | Statement: [RSMC Honolulu, typeOfWarningCenter, tropical cyclone warning center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWarningCenter Context triple: [RSMC Honolulu, typeOfWarningCenter, tropical cyclone warning center]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
centerType
chosen
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
C.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
D.
warningCall
Indicates that one entity initiates a call to another specifically to warn them about a danger, risk, or important cautionary information.
-
E.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
- F. None of above.
Provenance (3 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60a6623c8190ba43545544f58633 |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.