Triple

T22758784
Position Surface form Disambiguated ID Type / Status
Subject Imperial City of Tournai E562925 entity
Predicate locatedIn P40 FINISHED
Object Tournai 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: Tournai | Statement: [Imperial City of Tournai, locatedIn, Tournai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tournai
Context triple: [Imperial City of Tournai, locatedIn, Tournai]
  • A. Tournai chosen
    Tournai is a historic city in western Belgium, known for its medieval architecture, including a UNESCO-listed cathedral and belfry, and its strategic importance in European conflicts.
  • B. Courtrai
    Courtrai, known today as Kortrijk, is a historic city in western Belgium noted for its medieval architecture and role in several significant European conflicts.
  • C. Tournaisien
    Tournaisien is a regional variety of the Picard language traditionally spoken in and around the city of Tournai in Belgium.
  • D. Bouzincourt
    Bouzincourt is a small commune in northern France’s Somme department, known for its rural setting and World War I history.
  • E. Melincourt
    Melincourt is a small locality in Wales known for its scenic surroundings, including the nearby Melincourt Brook and waterfall.
  • 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_69e24552e11c81909c2d61578a558bd7 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17a7a8ca481909953dcd6fbcc5fcf completed April 29, 2026, 3:26 a.m.
Created at: April 17, 2026, 3:25 p.m.