Triple

T10657945
Position Surface form Disambiguated ID Type / Status
Subject Roeselare E251142 entity
Predicate hasTwinTown P919 FINISHED
Object Béthune E186103 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: Béthune | Statement: [Roeselare, hasTwinTown, Béthune]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Béthune
Context triple: [Roeselare, hasTwinTown, Béthune]
  • A. Béthune chosen
    Béthune is a historic town in northern France known for its medieval belfry and role as a regional center in the former County of Artois.
  • B. Berlencourt
    Berlencourt is a small commune in northern France, located within the Nord department in the Hauts-de-France region.
  • C. Breteuil
    Breteuil is a commune in northern France that serves as a local administrative and service hub for its surrounding rural area.
  • D. Mondercange
    Mondercange is a commune and small town in southwestern Luxembourg, known for hosting the headquarters and training center of the national football association.
  • E. Rocourt
    Rocourt is a district of Liège in present-day Belgium, historically notable as the site of the 1746 Battle of Rocoux during the War of the Austrian Succession.
  • 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_69d6aa5a4c4881908f39be6efe5981e5 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6e01643a88190abc7c16fd0f85e53 completed April 8, 2026, 11:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69d98857ec248190bb655d36981a000a completed April 10, 2026, 11:31 p.m.
Created at: April 8, 2026, 9:07 p.m.