Triple

T9737317
Position Surface form Disambiguated ID Type / Status
Subject Maaseik E236095 entity
Predicate borderedBy P224 FINISHED
Object Dilsen-Stokkem E636912 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: Dilsen-Stokkem | Statement: [Maaseik, borderedBy, Dilsen-Stokkem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dilsen-Stokkem
Context triple: [Maaseik, borderedBy, Dilsen-Stokkem]
  • A. Dilsen-Stokkem chosen
    Dilsen-Stokkem is a municipality in the Belgian province of Limburg, known for its location along the River Meuse and its mix of rural landscapes and small-town centers.
  • B. Diepenbeek
    Diepenbeek is a municipality in the Belgian province of Limburg, known for its blend of residential areas, industry, and the campus of Hasselt University.
  • C. Borgerhout
    Borgerhout is a densely populated, multicultural district of the Belgian city of Antwerp, known for its vibrant street life and diverse communities.
  • D. Lembeek
    Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
  • E. Willebroek
    Willebroek is a municipality in northern Belgium known for its canal connections and location between Brussels and Antwerp.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9ef032088190acd94c35b89e48b7 completed April 1, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d20d048c5081908c891633129dc5d6 completed April 5, 2026, 7:19 a.m.
Created at: March 30, 2026, 8:22 p.m.