Triple

T14336970
Position Surface form Disambiguated ID Type / Status
Subject Siege of Mons (1709) E355489 entity
Predicate hasLocation P40 FINISHED
Object Hainaut E86438 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: Hainaut | Statement: [Siege of Mons (1709), hasLocation, Hainaut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hainaut
Context triple: [Siege of Mons (1709), hasLocation, 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 (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_69d8278fa2108190bc0d0e7939c1eb03 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8c2241e48190a0c626b3d741966a completed April 14, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd46986758819088750150ad47bae1 completed May 8, 2026, 2:12 a.m.
Created at: April 10, 2026, 1:14 a.m.