Triple

T13449357
Position Surface form Disambiguated ID Type / Status
Subject judicial arrondissement of Kortrijk E320567 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Izegem E656791 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: Izegem | Statement: [judicial arrondissement of Kortrijk, hasJurisdictionOver, Izegem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Izegem
Context triple: [judicial arrondissement of Kortrijk, hasJurisdictionOver, Izegem]
  • A. Izegem chosen
    Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
  • B. Edegem
    Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
  • 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. 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.
  • E. Zottegem
    Zottegem is a city and municipality in East Flanders, Belgium, known for its historic center and its role as a regular feature in Flemish cycling races.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaef973b08190a3d7fe1c2a913cff completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7b8c49e9c819088e6e98aa53d05fa completed May 3, 2026, 9:06 p.m.
Created at: April 9, 2026, 9:41 p.m.