Triple
T37393833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Ellicott City flood |
E928792
|
entity |
| Predicate | approximateRainfall |
P89042
|
FINISHED |
| Object | over 6 inches in about 2 hours |
—
|
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: over 6 inches in about 2 hours | Statement: [2016 Ellicott City flood, approximateRainfall, over 6 inches in about 2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRainfall Context triple: [2016 Ellicott City flood, approximateRainfall, over 6 inches in about 2 hours]
-
A.
averageAnnualPrecipitation
Indicates the typical total amount of precipitation an entity receives over the course of a year, averaged across multiple years.
-
B.
rainfallLevel
chosen
Indicates the amount or intensity of rainfall occurring at a given place and time.
-
C.
hasHigherPrecipitationThan
Indicates that one location or time period experiences a greater amount of precipitation than another.
-
D.
collectsRainfallFor
Indicates that one entity gathers or measures rainfall on behalf of, or for the benefit of, another entity.
-
E.
rainfallReliability
Indicates how consistently and predictably rainfall occurs over time in a given area.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:16 p.m.