Triple

T1616611
Position Surface form Disambiguated ID Type / Status
Subject Windsor E34732 entity
Predicate twinTown P1072 FINISHED
Object Kortrijk E168511 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: Kortrijk | Statement: [Windsor, twinTown, Kortrijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kortrijk
Context triple: [Windsor, twinTown, Kortrijk]
  • A. Kortrijk chosen
    Kortrijk is a historic city in western Belgium known for its medieval architecture, textile industry heritage, and role in the Battle of the Golden Spurs.
  • B. Mechelen
    Mechelen is a historic city in the Flemish region of Belgium, known for its rich architectural heritage, medieval center, and prominent role in the Low Countries’ political and religious history.
  • C. Ghent
    Ghent is a historic city in the Flemish region of Belgium, known for its medieval architecture, canals, and role as a major cultural and economic center in the Middle Ages.
  • D. Vilvoorde
    Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
  • E. Antwerp
    Antwerp is a major Belgian port city on the River Scheldt, renowned as a global center for the diamond trade and its historic Flemish art and architecture.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a909abbec081908f95547471530ad5 completed March 5, 2026, 4:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69af83294c4881908411bc4f8649dbdd completed March 10, 2026, 2:34 a.m.
Created at: March 4, 2026, 7:28 p.m.