Triple

T1186665
Position Surface form Disambiguated ID Type / Status
Subject Maas E25262 entity
Predicate tributary P415 FINISHED
Object Geul E163435 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: Geul | Statement: [Maas, tributary, Geul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Geul
Context triple: [Maas, tributary, Geul]
  • A. Geul chosen
    The Geul is a small river in the southeastern Netherlands and eastern Belgium, known for flowing through the hilly Limburg landscape and picturesque villages before joining the Meuse.
  • B. Waal
    The Waal is a major distributary branch of the Rhine River in the Netherlands, serving as an important waterway for shipping and part of the country’s main river system.
  • C. Dommel
    The Dommel is a river in the southern Netherlands and northern Belgium that flows through cities including Eindhoven before joining the Dieze.
  • D. Reimerswaal
    Reimerswaal is a coastal municipality in the Dutch province of Zeeland, known for its agricultural landscape and location along the Eastern Scheldt estuary.
  • E. Rupel
    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.
  • 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_69a49427d98881908646d6c63b8cea1e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd5578b08190bbe4089857fbf166 completed March 1, 2026, 10:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad231945048190be6536b4a71334aa completed March 8, 2026, 7:19 a.m.
Created at: March 1, 2026, 7:45 p.m.