Triple

T35395125
Position Surface form Disambiguated ID Type / Status
Subject Upper Olona watershed E1023050 entity
Predicate watercourseTypeServed P195326 FINISHED
Object river upper course 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 upper course | Statement: [Upper Olona watershed, watercourseTypeServed, river upper course]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: watercourseTypeServed
Context triple: [Upper Olona watershed, watercourseTypeServed, river upper course]
  • A. waterwayServed
    Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
  • B. watercourseFor
    Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
  • C. sourceOfWatercourse
    Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
  • D. watercourseId
    Indicates the identifier that uniquely associates an entity with a specific watercourse (such as a river, stream, or canal).
  • E. watercourseSupports
    Indicates that a watercourse provides the necessary conditions or resources to sustain another entity, process, or activity.
  • F. None of above. chosen

Provenance (4 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_69f76df34ba48190bd80f0814cdcd540 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fdbaa226708190b8ed96e93aad38de completed May 8, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69fdb58b07e48190837e00966de050d4 completed May 8, 2026, 10:06 a.m.
PDg Predicate description generation batch_69fdbaa1313081908beea28a5597ae40 completed May 8, 2026, 10:27 a.m.
Created at: May 3, 2026, 4:03 p.m.