Triple
T175982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA Weather Radio |
E3575
|
entity |
| Predicate | supportsAlertingFor |
P203
|
FINISHED |
| Object | tornado 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: tornado warnings | Statement: [NOAA Weather Radio, supportsAlertingFor, tornado warnings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlertingFor Context triple: [NOAA Weather Radio, supportsAlertingFor, tornado warnings]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
C.
supportsActivity
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
canReport
Indicates that one entity has the ability or permission to report on, or submit a report about, 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e497788190aeb61d981efb4d1d |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.