Triple

T11886946
Position Surface form Disambiguated ID Type / Status
Subject Mulpus Brook E282807 entity
Predicate hasHydrologicUnitCode P59675 FINISHED
Object 01070002 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: 01070002 | Statement: [Mulpus Brook, hasHydrologicUnitCode, 01070002]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHydrologicUnitCode
Context triple: [Mulpus Brook, hasHydrologicUnitCode, 01070002]
  • A. hydrologicUnitCode chosen
    Indicates the standardized hydrologic unit identifier that specifies the drainage or watershed area associated with a given geographic feature or location.
  • B. hydrologicCodeSystem
    Indicates the classification or coding system used to identify and organize hydrologic or water-related features.
  • C. hasHydrologicalRegime
    Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
  • D. hasHydrologicalFunction
    Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
  • E. hasHydrologicalType
    Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
  • 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d3a13370819086386fecb99e4f0b completed April 10, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69d8bb2fca4481909893f3428b0871ac completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:44 p.m.