Triple
T550167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount St. Helens |
E11819
|
entity |
| Predicate | 1980LateralBlastDirection |
P15608
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Mount St. Helens, 1980LateralBlastDirection, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1980LateralBlastDirection Context triple: [Mount St. Helens, 1980LateralBlastDirection, north]
-
A.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
B.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
-
C.
directionalOperation
Indicates an operation whose effect depends on or is applied along a specific direction or orientation between entities.
-
D.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
E.
involvesProjectile
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49901e4e481909a5ed93c21ab37bd |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.