Triple

T3905827
Position Surface form Disambiguated ID Type / Status
Subject Lys E87201 entity
Predicate hasCityOnBank P7935 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: [Lys, hasCityOnBank, Comines]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Comines
Context triple: [Lys, hasCityOnBank, 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. Pétange
    Pétange is a commune in southwestern Luxembourg known for its proximity to the borders with Belgium and France and its role as a local transport and industrial hub.
  • 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_69aed9424514819086e9c58adde6652d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeed1102b08190a9f5087ff9be0358 completed March 9, 2026, 3:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5a82c551c8190a97fdc5a96cf131c completed March 14, 2026, 6:25 p.m.
Created at: March 9, 2026, 3:22 p.m.