Triple

T21206875
Position Surface form Disambiguated ID Type / Status
Subject Belfry of Charleroi E522609 entity
Predicate locatedIn P40 FINISHED
Object Hainaut 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: Hainaut | Statement: [Belfry of Charleroi, locatedIn, Hainaut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hainaut
Context triple: [Belfry of Charleroi, locatedIn, Hainaut]
  • A. Hainaut chosen
    Hainaut is a historical region in western Europe, now divided between Belgium and France, known for its medieval heritage and role as a frequent battleground in European conflicts.
  • B. Putot-en-Bessin
    Putot-en-Bessin is a small commune in the Calvados department of Normandy in northwestern France, known for its rural character and World War II history.
  • C. Barrois
    Barrois is a historical region in northeastern France that formed the core territory of the medieval County of Bar.
  • D. Cernières
    Cernières is a small locality situated within the canton of Breteuil in northern France.
  • E. Creillois
    Creillois is the French term for inhabitants of the town of Creil in northern France.
  • 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73435322c8190bf4156fbd14edc5c completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:24 p.m.