Triple

T20470833
Position Surface form Disambiguated ID Type / Status
Subject canton of Senlis E502187 entity
Predicate contains P35 FINISHED
Object Mortefontaine 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: Mortefontaine | Statement: [canton of Senlis, contains, Mortefontaine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mortefontaine
Context triple: [canton of Senlis, contains, Mortefontaine]
  • A. Mortefontaine, France chosen
    Mortefontaine, France is a commune in the Oise department in northern France, historically notable as the site where the 1800 Convention of Mortefontaine was signed to normalize relations between France and the United States.
  • B. Chaudfontaine
    Chaudfontaine is a Belgian municipality in the Walloon region, noted for its mineral water springs and proximity to the city of Liège.
  • C. Goffontaine
    Goffontaine is a locality within the municipality of Pepinster in the province of Liège, Belgium.
  • D. Orgeval
    Orgeval is a district in the city of Reims, France, known in part for serving as a terminus of the Reims tramway network.
  • E. Orgeval
    Orgeval is a commune in the Yvelines department of north-central France, known for its residential character and proximity to the Paris metropolitan 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_69e0b4ae5f1081908768b0c9a3a0bf38 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e699608d7c8190910217817e789915 completed April 20, 2026, 9:23 p.m.
Created at: April 16, 2026, 11:33 a.m.