Triple

T12407045
Position Surface form Disambiguated ID Type / Status
Subject Swiss Plateau hydrological network E296414 entity
Predicate includesWaterBodyType P92225 FINISHED
Object river 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: river | Statement: [Swiss Plateau hydrological network, includesWaterBodyType, river]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesWaterBodyType
Context triple: [Swiss Plateau hydrological network, includesWaterBodyType, river]
  • A. hasBodyOfWaterType chosen
    Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
  • B. appliesToWaterBody
    Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
  • C. locatedInWaterBodyType
    Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
  • D. isInlandWaterBodyOf
    Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
  • E. hasAreaWaterBody
    Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
  • 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_69d6ad9f464c81909db36d7e96e34b9e completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94e1888b48190bd750f839a26e99e completed April 10, 2026, 7:23 p.m.
PD Predicate disambiguation batch_69d94d354b488190adc83fb4f2770dd5 completed April 10, 2026, 7:19 p.m.
Created at: April 8, 2026, 9:55 p.m.