Triple

T7038082
Position Surface form Disambiguated ID Type / Status
Subject Geul E163435 entity
Predicate flowsThrough P225 FINISHED
Object Meerssen E691114 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: Meerssen | Statement: [Geul, flowsThrough, Meerssen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meerssen
Context triple: [Geul, flowsThrough, Meerssen]
  • A. Meerssen chosen
    Meerssen is a historic town and municipality in the Dutch province of Limburg, known for its medieval basilica and scenic location near Maastricht.
  • B. Maasbracht
    Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
  • C. Wateringen
    Wateringen is a town in the western Netherlands that forms part of the municipality of Westland in the province of South Holland.
  • D. Zierikzee
    Zierikzee is a historic Dutch town on the island of Schouwen-Duiveland in Zeeland, known for its well-preserved medieval center and maritime heritage.
  • E. Sommelsdijk
    Sommelsdijk is a village in the Netherlands located on the island of Goeree-Overflakkee in the province of South Holland.
  • 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_69c6885e7c1c8190be32a8f79ab4e0cf completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e223077c819097992089fa83c563 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c98564d32881908ebdeb2aa41da4f7 completed March 29, 2026, 8:02 p.m.
Created at: March 27, 2026, 2:36 p.m.