Triple

T6203375
Position Surface form Disambiguated ID Type / Status
Subject Juliana Canal E138690 entity
Predicate hasLock P2431 FINISHED
Object Borgharen lock E576380 NE 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: Borgharen lock | Statement: [Juliana Canal, hasLock, Borgharen lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borgharen lock
Context triple: [Juliana Canal, hasLock, Borgharen lock]
  • A. Borgharen lock complex chosen
    The Borgharen lock complex is a major hydraulic structure near Maastricht in the Netherlands that regulates water levels and navigation between the Meuse River and the Juliana Canal.
  • B. Weurt lock
    Weurt lock is a major Dutch navigation lock complex near Nijmegen that regulates water levels and ship traffic between the Waal River and the Amsterdam–Rhine Canal.
  • C. Amerongen weir
    Amerongen weir is a major hydraulic structure on the Nederrijn in the Netherlands that regulates river water levels and flow through a system of floodgates.
  • D. Wijnegem locks
    The Wijnegem locks are a major lock complex in Wijnegem, Belgium, that regulates water levels and ship traffic on the Albert Canal near Antwerp.
  • E. Driel weir
    Driel weir is a key hydraulic structure in the Netherlands that regulates water levels and flow in the Rhine delta to support flood control, navigation, and water management.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c008acbea48190991c6b834bb45d65 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0626c23f481909d2b5b0a75c2ffff completed March 22, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c20d9def0481909dc252d8a0ace45e completed March 24, 2026, 4:05 a.m.
Created at: March 22, 2026, 4:20 p.m.