Triple

T1101189
Position Surface form Disambiguated ID Type / Status
Subject Munttoren E24383 entity
Predicate locatedNear P294 FINISHED
Object Amstel river E4253 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: Amstel river | Statement: [Munttoren, locatedNear, Amstel river]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amstel river
Context triple: [Munttoren, locatedNear, Amstel river]
  • A. Amstel River chosen
    The Amstel River is a historic waterway in the Netherlands that flows through and gives its name to the city of Amsterdam.
  • B. 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.
  • C. 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.
  • D. Hollandsche IJssel
    Hollandsche IJssel is a river in the western Netherlands that flows through the provinces of South Holland and Utrecht and plays a role in regional water management and flood control.
  • E. Nederrijn
    The Nederrijn is a major distributary branch of the Rhine River in the Netherlands, flowing through cities such as Arnhem and forming an important part of the Dutch river system.
  • 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b9c079f48190a0e0ddda182f7a01 completed March 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad089d492881909c6ef4519c087386 completed March 8, 2026, 5:26 a.m.
Created at: March 1, 2026, 7:43 p.m.