Triple

T21785301
Position Surface form Disambiguated ID Type / Status
Subject Hoge Kempen National Park E537819 entity
Predicate nearestCity P350 FINISHED
Object Maasmechelen 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: Maasmechelen | Statement: [Hoge Kempen National Park, nearestCity, Maasmechelen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maasmechelen
Context triple: [Hoge Kempen National Park, nearestCity, Maasmechelen]
  • A. Maasmechelen chosen
    Maasmechelen is a municipality in the Belgian province of Limburg, known for its proximity to the Meuse River and the popular Maasmechelen Village outlet shopping center.
  • B. Maasgouw
    Maasgouw is a municipality in the Dutch province of Limburg, known for its historic villages and location along the river Maas.
  • C. Maasmond
    Maasmond is the Dutch name for the estuary where the River Meuse (Maas) flows into the North Sea, an important maritime gateway in the Netherlands.
  • D. Binnenmaas
    Binnenmaas was a former municipality in the Dutch province of South Holland, named after the nearby lake and comprising several villages in the Hoeksche Waard region.
  • E. Maasdonk
    Maasdonk was a former municipality in the Dutch province of North Brabant that was merged into the municipality of Oss in 2015.
  • 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_69e0c47198f881908cb0d237266c10e9 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04630f4f08190910b9e499a4249ca completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:52 p.m.