Triple

T27451255
Position Surface form Disambiguated ID Type / Status
Subject Angstel E692447 entity
Predicate connectsWatercourse P20872 FINISHED
Object Vecht 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: Vecht | Statement: [Angstel, connectsWatercourse, Vecht]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsWatercourse
Context triple: [Angstel, connectsWatercourse, Vecht]
  • 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. hydrologicallyConnectedTo chosen
    Indicates that two water bodies or hydrological features are linked such that water can flow or be transferred between them, directly or indirectly, through the hydrological system.
  • C. watercourseFor
    Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
  • D. hasWatercourseType
    Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
  • E. isMajorWatercourseOf
    Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
  • 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_69ef5206c9248190b5975c2a7f9d229c completed April 27, 2026, 12:09 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: April 27, 2026, 12:47 p.m.