Triple
T32551254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Johnstown Flood of 1889 |
E831977
|
entity |
| Predicate | speedOfFloodWave |
P155514
|
FINISHED |
| Object | up to about 40 miles per hour |
—
|
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: up to about 40 miles per hour | Statement: [Great Johnstown Flood of 1889, speedOfFloodWave, up to about 40 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedOfFloodWave Context triple: [Great Johnstown Flood of 1889, speedOfFloodWave, up to about 40 miles per hour]
-
A.
floodPeakDischarge
Indicates the maximum rate of water flow occurring at the peak of a flood event in a river or channel.
-
B.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
C.
floodFrequency
Indicates how often flooding occurs or is expected to occur at a given location or under specified conditions.
-
D.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
-
E.
flowSpeed
chosen
Indicates the rate at which a fluid or medium moves through a given point or along a path over time.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c70200819080339dcbe1a4088d |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.