Triple

T37393836
Position Surface form Disambiguated ID Type / Status
Subject 2016 Ellicott City flood E928792 entity
Predicate riverOrStreamInvolved P75568 FINISHED
Object Tiber River (Ellicott City) NE NERFINISHED

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: Tiber River (Ellicott City) | Statement: [2016 Ellicott City flood, riverOrStreamInvolved, Tiber River (Ellicott City)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riverOrStreamInvolved
Context triple: [2016 Ellicott City flood, riverOrStreamInvolved, Tiber River (Ellicott City)]
  • A. isWatercourseOf
    Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
  • B. hasRiverActivity
    Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
  • C. flowsIntoBodyOfWaterAt
    Indicates that one body of water moves or drains into another body of water at a specific location or point.
  • D. riverPhenomenon
    Indicates a natural event, condition, or process that occurs in or directly affects a river.
  • E. riverConcerned chosen
    Indicates a relationship in which a river is the primary focus or subject of concern, attention, or impact in a given context.
  • 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_69fbc36ce1f88190a7fa1656b714e107 completed May 6, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69fbbd13595c81908719f52c3d37a7e8 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:16 p.m.