Triple

T1270913
Position Surface form Disambiguated ID Type / Status
Subject Lek E15705 entity
Predicate tributaryTo P415 FINISHED
Object Nieuwe Maas E26053 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: Nieuwe Maas | Statement: [Lek, tributaryTo, Nieuwe Maas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nieuwe Maas
Context triple: [Lek, tributaryTo, Nieuwe Maas]
  • A. Nieuwe Maas chosen
    The Nieuwe Maas is a major distributary of the Rhine and Meuse rivers flowing through Rotterdam in the Netherlands, forming an important part of the region’s busy inland waterway network.
  • B. Oude Maas
    The Oude Maas is a major distributary river in the western Netherlands that forms part of the complex Rhine–Meuse–Scheldt delta system.
  • C. Beneden Merwede
    Beneden Merwede is a major distributary branch of the Rhine–Meuse river system in the western Netherlands, important for inland shipping and regional water management.
  • D. Vaartsche Rijn
    Vaartsche Rijn is a historic canal in the Dutch province of Utrecht that connects the city of Utrecht with the Lower Rhine and forms part of its inland waterway network.
  • E. Amstel River
    The Amstel River is a historic waterway in the Netherlands that flows through and gives its name to the city of Amsterdam.
  • 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_69a4935a94308190bb92555b79032824 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4c06ae7b88190a1e0b5232d84a7b1 completed March 1, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad8a9f91808190b44715dc3df31cc3 completed March 8, 2026, 2:41 p.m.
Created at: March 1, 2026, 7:50 p.m.