Triple

T6793632
Position Surface form Disambiguated ID Type / Status
Subject South Limburg E155996 entity
Predicate contains P35 FINISHED
Object Valkenburg aan de Geul E380675 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: Valkenburg aan de Geul | Statement: [South Limburg, contains, Valkenburg aan de Geul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Valkenburg aan de Geul
Context triple: [South Limburg, contains, Valkenburg aan de Geul]
  • A. Valkenburg aan de Geul chosen
    Valkenburg aan de Geul is a historic town in the hilly Limburg region of the Netherlands, known for its cycling heritage, marlstone caves, and medieval castle ruins.
  • B. Veldhoven
    Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
  • C. Hansweert
    Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
  • D. Valkenburg
    Valkenburg is a village in the Dutch province of South Holland, known for its historic charm and proximity to the North Sea coast.
  • E. Vollenhove
    Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
  • 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_69c6881844448190a65822d9b39d7f88 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2af6f908190809e39b73894e513 completed March 27, 2026, 6:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad6644f4819080db0a3981470d96 completed March 28, 2026, 10:28 a.m.
Created at: March 27, 2026, 2:15 p.m.