Triple

T21164047
Position Surface form Disambiguated ID Type / Status
Subject Helmond E521510 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Laarbeek 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: Laarbeek | Statement: [Helmond, hasNeighbouringMunicipality, Laarbeek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laarbeek
Context triple: [Helmond, hasNeighbouringMunicipality, Laarbeek]
  • A. Laarbeek chosen
    Laarbeek is a municipality in the southern Netherlands, in the province of North Brabant, comprising several villages including Beek en Donk, Lieshout, and Aarle-Rixtel.
  • B. Meerbeke
    Meerbeke is a village in East Flanders, Belgium, best known for having long served as the traditional finish town of the Tour of Flanders cycling race.
  • C. Linkebeek
    Linkebeek is a small Flemish municipality in the Belgian province of Flemish Brabant, located just south of Brussels.
  • D. Michelbeke
    Michelbeke is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural character and cycling-friendly landscape.
  • E. 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.
  • 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_69e0b50d1ea481909c07e63c3ead9316 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72533fe88819082e14d71c36140be completed April 21, 2026, 7:20 a.m.
Created at: April 16, 2026, 2:59 p.m.