Triple

T21745447
Position Surface form Disambiguated ID Type / Status
Subject Battle of Baugé E536774 entity
Predicate location P40 FINISHED
Object Baugé 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: Baugé | Statement: [Battle of Baugé, location, Baugé]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baugé
Context triple: [Battle of Baugé, location, Baugé]
  • A. Baugé-en-Anjou chosen
    Baugé-en-Anjou is a commune in western France known for its historic town center and château, located in the Maine-et-Loire department of the Pays de la Loire region.
  • B. Fontaine-au-Bois
    Fontaine-au-Bois is a small commune in the Nord department of northern France, situated within the administrative area of the Hauts-de-France region.
  • C. Guignicourt
    Guignicourt is a commune in northern France located in the Aisne department in the Hauts-de-France region.
  • D. Langeac
    Langeac is a small commune in south-central France, situated in the Haute-Loire department within the Auvergne-Rhône-Alpes region.
  • 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_69e0c46df5448190b4322127ffc4c690 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a76540c8190b91a67f4a70869fb completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:49 p.m.