Triple

T18162417
Position Surface form Disambiguated ID Type / Status
Subject Aire-sur-la-Lys E434798 entity
Predicate locatedNear P294 FINISHED
Object Béthune 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: Béthune | Statement: [Aire-sur-la-Lys, locatedNear, Béthune]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Béthune
Context triple: [Aire-sur-la-Lys, locatedNear, 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. Beaunoir
    Beaunoir is a rare white wine grape variety, historically cultivated in parts of Europe and known primarily through its role in old viticultural lineages.
  • C. Berlencourt
    Berlencourt is a small commune in northern France, located within the Nord department in the Hauts-de-France region.
  • D. Génicourt
    Génicourt is a French commune that forms part of the administrative area of the canton of Vauréal.
  • E. Breteuil
    Breteuil is a commune in northern France that serves as a local administrative and service hub for its surrounding rural area.
  • 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec32530819099d906640a07e92c completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 10:30 a.m.