Triple

T17717942
Position Surface form Disambiguated ID Type / Status
Subject Schelle E442254 entity
Predicate locatedOn P40 FINISHED
Object Rupel River 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: Rupel River | Statement: [Schelle, locatedOn, Rupel River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rupel River
Context triple: [Schelle, locatedOn, Rupel River]
  • A. Rupel chosen
    The Rupel is a short river in northern Belgium that flows through the province of Antwerp and joins the Scheldt near the town of Rupelmonde.
  • B. River Dender
    The River Dender is a waterway in Belgium that flows through Wallonia and Flanders before joining the Scheldt, historically shaping the towns and regions along its course.
  • C. Oldetrijne
    Oldetrijne is a small village in the municipality of Weststellingwerf in the Dutch province of Friesland.
  • D. River Zenne
    The River Zenne is a small Belgian river that flows through Brussels and surrounding towns, historically shaping the region’s development and urban landscape.
  • E. Geul River
    The Geul River is a small, winding river in the southeastern Netherlands and eastern Belgium, known for its scenic valleys, historic watermills, and role in shaping the hilly landscape of South Limburg.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e474834aec81909ab7e8224c5a39d7 completed April 19, 2026, 6:21 a.m.
Created at: April 10, 2026, 10:06 a.m.