Triple
T7777854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSSL |
E221438
|
entity |
| Predicate | focusesOnPhenomenon |
P31
|
FINISHED |
| Object | severe thunderstorms |
—
|
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: severe thunderstorms | Statement: [NSSL, focusesOnPhenomenon, severe thunderstorms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnPhenomenon Context triple: [NSSL, focusesOnPhenomenon, severe thunderstorms]
-
A.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:16 p.m.