Triple

T16219315
Position Surface form Disambiguated ID Type / Status
Subject Dilbeek E393676 entity
Predicate borderedBy P224 FINISHED
Object Sint-Pieters-Leeuw E393677 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: Sint-Pieters-Leeuw | Statement: [Dilbeek, borderedBy, Sint-Pieters-Leeuw]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sint-Pieters-Leeuw
Context triple: [Dilbeek, borderedBy, Sint-Pieters-Leeuw]
  • A. Sint-Pieters-Leeuw chosen
    Sint-Pieters-Leeuw is a municipality in the Belgian province of Flemish Brabant, known for its mix of suburban neighborhoods, rural landscapes, and landmarks such as the Coloma rose garden.
  • B. Lembeek
    Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
  • C. Sint-Martens-Leerne
    Sint-Martens-Leerne is a village in East Flanders, Belgium, known as a rural residential community within the municipality of Deinze.
  • D. Willebroek
    Willebroek is a municipality in northern Belgium known for its canal connections and location between Brussels and Antwerp.
  • E. Lubbeek
    Lubbeek is a municipality in the Flemish Brabant province of Belgium, situated in the Arrondissement of Leuven.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e227f95de081908e1abe32d281dbe7 completed April 17, 2026, 12:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0007987cd881908ebc01141028c0a5 completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 5:03 a.m.