Triple

T15774528
Position Surface form Disambiguated ID Type / Status
Subject arrondissement of Lille E382452 entity
Predicate contains P35 FINISHED
Object Comines E421252 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: Comines | Statement: [arrondissement of Lille, contains, Comines]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Comines
Context triple: [arrondissement of Lille, contains, Comines]
  • A. Comines chosen
    Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
  • B. Sarreguemines
    Sarreguemines is a town in northeastern France near the German border, historically known for its ceramics and faience production.
  • C. Mondercange
    Mondercange is a commune and small town in southwestern Luxembourg, known for hosting the headquarters and training center of the national football association.
  • D. 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.
  • E. Berlencourt
    Berlencourt is a small commune in northern France, located within the Nord department in the Hauts-de-France region.
  • 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_69d86da09a10819082fe9797b23e4664 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e05198c1588190a65e23c18443eb5c completed April 16, 2026, 3:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffb59779788190a393237f5293fe8d completed May 9, 2026, 10:30 p.m.
Created at: April 10, 2026, 4:47 a.m.