Triple

T14252539
Position Surface form Disambiguated ID Type / Status
Subject Zwolle E353304 entity
Predicate twinCity P1072 FINISHED
Object Oudenaarde E100113 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: Oudenaarde | Statement: [Zwolle, twinCity, Oudenaarde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oudenaarde
Context triple: [Zwolle, twinCity, Oudenaarde]
  • A. Oudenarde chosen
    Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
  • B. Kerkrade
    Kerkrade is a town in the southeastern Netherlands, near the German border, known for its mining history and the international music festival WMC Kerkrade.
  • C. Izegem
    Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
  • 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. Aalst
    Aalst is a historic city in the Belgian province of East Flanders, known for its textile industry and famous annual carnival.
  • 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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6297f38c819090d7c7fd8bfa2e9e completed April 14, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe8bbd051c8190a89f9801a7b08b2d completed May 9, 2026, 1:19 a.m.
Created at: April 10, 2026, 1:08 a.m.