Triple

T20581871
Position Surface form Disambiguated ID Type / Status
Subject Lys (Leie) E505676 entity
Predicate flowsThrough P225 FINISHED
Object Harelbeke 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: Harelbeke | Statement: [Lys (Leie), flowsThrough, Harelbeke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harelbeke
Context triple: [Lys (Leie), flowsThrough, Harelbeke]
  • A. Harelbeke chosen
    Harelbeke is a municipality in the Belgian province of West Flanders, known for its historic town center and as a regular host of the E3 Saxo Bank Classic cycling race.
  • B. Roeselare
    Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
  • C. Merelbeke
    Merelbeke is a municipality in East Flanders, Belgium, known in part for hosting Ghent University's Faculty of Veterinary Medicine.
  • D. 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.
  • 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 (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_69e0b4b9669c8190b8e81fc72817d42c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a90f7e34819086b1745dcd53ba25 completed April 20, 2026, 10:30 p.m.
Created at: April 16, 2026, 11:40 a.m.