Triple

T21557114
Position Surface form Disambiguated ID Type / Status
Subject Vilvoorde E531920 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Meise 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: Meise | Statement: [Vilvoorde, hasNeighbouringMunicipality, Meise]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meise
Context triple: [Vilvoorde, hasNeighbouringMunicipality, Meise]
  • A. Meise chosen
    Meise is a municipality in the Belgian province of Flemish Brabant, known for hosting the National Botanic Garden of Belgium.
  • B. Diegem
    Diegem is a village in Flemish Brabant, Belgium, known for its proximity to Brussels Airport and its role as a commercial and office hub.
  • C. Werchter
    Werchter is a village in the Flemish Brabant province of Belgium, best known for hosting the annual Rock Werchter music festival.
  • D. Ixelles
    Ixelles is a vibrant, multicultural municipality of the Brussels-Capital Region in Belgium, known for its Art Nouveau architecture, lively student population, and cultural institutions.
  • E. Auderghem
    Auderghem is a residential municipality in the southeastern part of the Brussels-Capital Region in Belgium, known for its green spaces and proximity to major European institutions.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e04b048190ac3a9913094b4625 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.