Triple

T20497470
Position Surface form Disambiguated ID Type / Status
Subject Eisbach E502910 entity
Predicate hasFlowControl P3686 FINISHED
Object weirs and hydraulic structures 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: weirs and hydraulic structures | Statement: [Eisbach, hasFlowControl, weirs and hydraulic structures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFlowControl
Context triple: [Eisbach, hasFlowControl, weirs and hydraulic structures]
  • A. flowControl chosen
    Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
  • B. hasFlowRegime
    Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
  • C. hasFlowLayer
    Indicates that one entity possesses or is associated with a specific flow layer within a layered or stratified structure.
  • D. regulatesFlowBetween
    Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
  • E. hasControlFields
    Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cbefe4c819098af5bfd4d92341d completed April 20, 2026, 9:38 p.m.
PD Predicate disambiguation batch_69e59fcdf6e08190a604204615dc56e6 completed April 20, 2026, 3:38 a.m.
Created at: April 16, 2026, 11:35 a.m.