Triple

T18710818
Position Surface form Disambiguated ID Type / Status
Subject Wakken E457506 entity
Predicate locatedNear P294 FINISHED
Object Waregem 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: Waregem | Statement: [Wakken, locatedNear, Waregem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waregem
Context triple: [Wakken, locatedNear, Waregem]
  • A. Waregem chosen
    Waregem is a city in the Belgian province of West Flanders, known for its historical World War I sites and equestrian traditions.
  • B. Roermond
    Roermond is a historic city in the southeastern Netherlands known for its medieval architecture, prominent churches, and large designer outlet shopping center.
  • C. Venray
    Venray is a town and municipality in the Dutch province of Limburg, known for its historic center and role in World War II.
  • D. Wommelgem
    Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
  • E. Torhout
    Torhout is a small city in West Flanders, Belgium, known for its educational institutions and its location near Bruges.
  • 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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5671b34508190b6180f7d6ad50a58 completed April 19, 2026, 11:36 p.m.
Created at: April 10, 2026, 11:50 a.m.