Triple

T1213420
Position Surface form Disambiguated ID Type / Status
Subject Nieuwe Maas E26053 entity
Predicate tributaryTo P415 FINISHED
Object Nieuwe Waterweg and Het Scheur system 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: Nieuwe Waterweg and Het Scheur system | Statement: [Nieuwe Maas, tributaryTo, Nieuwe Waterweg and Het Scheur system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tributaryTo
Context triple: [Nieuwe Maas, tributaryTo, Nieuwe Waterweg and Het Scheur system]
  • A. tributary chosen
    Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
  • B. drainsInto
    Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
  • C. hydrologicallyConnectedTo
    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.
  • D. waterwayServed
    Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
  • E. mouthOfTheWatercourse
    Indicates the location where a watercourse ends and flows into a larger body of water.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be024e448190ba263a0cc5cc9cd5 completed March 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69a4bb62a7c08190a79dcb6ff72ac99b completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:46 p.m.