Triple

T20974280
Position Surface form Disambiguated ID Type / Status
Subject river Maas E516582 entity
Predicate hasMajorTributary P415 FINISHED
Object Vesdre 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: Vesdre | Statement: [river Maas, hasMajorTributary, Vesdre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vesdre
Context triple: [river Maas, hasMajorTributary, Vesdre]
  • A. Vesdre chosen
    The Vesdre is a river in eastern Belgium that flows through the Ardennes and Liège region before joining the Meuse.
  • B. 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.
  • C. Lierelva
    Lierelva is a river in Norway that flows through Lier municipality before joining the larger Drammenselva river.
  • D. Dommel
    The Dommel is a river in the southern Netherlands and northern Belgium that flows through cities including Eindhoven before joining the Dieze.
  • E. Niederscheld
    Niederscheld is a village and district of the town of Dillenburg in the Lahn-Dill-Kreis of Hesse, Germany.
  • 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_69e0b4fee5ac8190875fa9ceba1a5e5e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fba307d88190b728544d1b6d0bb6 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:46 p.m.