Triple

T13739621
Position Surface form Disambiguated ID Type / Status
Subject Geraardsbergen E330048 entity
Predicate locatedNear P294 FINISHED
Object Aalst E527486 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: Aalst | Statement: [Geraardsbergen, locatedNear, Aalst]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aalst
Context triple: [Geraardsbergen, locatedNear, Aalst]
  • A. Aalst chosen
    Aalst is a historic city in the Belgian province of East Flanders, known for its textile industry and famous annual carnival.
  • B. Torhout
    Torhout is a small city in West Flanders, Belgium, known for its educational institutions and its location near Bruges.
  • C. Wommelgem
    Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
  • D. Izegem
    Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
  • E. Harelbeke
    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.
  • 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_69d80772315881908f980cae40d91664 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69de0204d50c8190a5413cc9a1b26e14 completed April 14, 2026, 8:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd6474da3081909be6b892ef8cc73e completed May 8, 2026, 4:20 a.m.
Created at: April 9, 2026, 9:55 p.m.