Triple
T5714629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1900 Galveston hurricane |
E125991
|
entity |
| Predicate | warningSystem |
P23340
|
FINISHED |
| Object | limited and inadequate hurricane warnings |
—
|
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: limited and inadequate hurricane warnings | Statement: [1900 Galveston hurricane, warningSystem, limited and inadequate hurricane warnings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningSystem Context triple: [1900 Galveston hurricane, warningSystem, limited and inadequate hurricane warnings]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
C.
warningCall
Indicates that one entity initiates a call to another specifically to warn them about a danger, risk, or important cautionary information.
-
D.
alertSystem
chosen
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.