Triple

T13048470
Position Surface form Disambiguated ID Type / Status
Subject Condroz E327385 entity
Predicate containsSettlement P847 FINISHED
Object Fosses-la-Ville E758729 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: Fosses-la-Ville | Statement: [Condroz, containsSettlement, Fosses-la-Ville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fosses-la-Ville
Context triple: [Condroz, containsSettlement, Fosses-la-Ville]
  • A. Fosses-la-Ville chosen
    Fosses-la-Ville is a historic town and municipality in Wallonia, Belgium, known for its medieval heritage and religious sites.
  • B. Fauvillers
    Fauvillers is a rural municipality in the province of Luxembourg in Wallonia, Belgium, known for its small villages and countryside landscapes.
  • C. Villers-la-Ville
    Villers-la-Ville is a Belgian municipality best known for the ruins of its medieval Cistercian abbey, a major historical and tourist site in Wallonia.
  • D. Berlencourt
    Berlencourt is a small commune in northern France, located within the Nord department in the Hauts-de-France region.
  • E. Mons-en-Barœul
    Mons-en-Barœul is a suburban commune in northern France that forms part of the Lille metropolitan area.
  • 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980b8811c81908577f092e2736610 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ff02c1448190b0b41beb427fae23 completed May 3, 2026, 7:53 a.m.
Created at: April 9, 2026, 8:57 p.m.