Triple

T16874123
Position Surface form Disambiguated ID Type / Status
Subject Comines E421252 entity
Predicate hasPart P35 FINISHED
Object Comines, Nord 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, Nord | Statement: [Comines, hasPart, Comines, Nord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Comines, Nord
Context triple: [Comines, hasPart, Comines, Nord]
  • 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. Douaumont, Meuse
    Douaumont, Meuse is a small commune in northeastern France best known as the site of major World War I battles and the nearby Fort Douaumont and Douaumont Ossuary.
  • D. Gerpinnes
    Gerpinnes is a municipality in the Walloon region of Belgium, known for its rural character and traditional Saint-Roch procession.
  • E. Marche-en-Famenne
    Marche-en-Famenne is a historic town in the Wallonia region of Belgium, known for its preserved old center and role as a local administrative and commercial 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_69d889d470fc8190b4aec199636c0c56 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3b7f5290481909e0fd0af30935fcd completed April 18, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7a27f548190963c35f40f4420f8 completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:29 a.m.