Triple

T14084671
Position Surface form Disambiguated ID Type / Status
Subject Yalding E338959 entity
Predicate locatedNearRiver P165 FINISHED
Object River Beult E267219 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: River Beult | Statement: [Yalding, locatedNearRiver, River Beult]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Beult
Context triple: [Yalding, locatedNearRiver, River Beult]
  • A. River Beult chosen
    River Beult is a lowland river in Kent, England, known for its meandering course through rural farmland before joining the River Medway.
  • B. river Gouwe
    The river Gouwe is a canalised river in South Holland, Netherlands, that serves as an important waterway connecting several towns and facilitating regional transport.
  • C. 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.
  • D. Heiligenbergerbeek
    Heiligenbergerbeek is a small stream in the Netherlands that flows through the Randenbroek area of Amersfoort.
  • E. 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.
  • 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ede40048190b465e909565730c1 completed April 14, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb676620481908ed2fa5687a21866 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.