Triple

T17108184
Position Surface form Disambiguated ID Type / Status
Subject Siege of Compiègne E415153 entity
Predicate location P40 FINISHED
Object Compiègne NE ONNED1

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: Compiègne | Statement: [Siege of Compiègne, location, Compiègne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Compiègne
Context triple: [Siege of Compiègne, location, Compiègne]
  • A. Compiegne chosen
    Compiègne is a historic city in northern France known for its royal château, forest, and role in significant events such as the signing of the 1918 Armistice.
  • B. Creil
    Creil is a commuter town in northern France’s Oise department, known as a regional rail hub connecting Paris with Picardy via major train and RER lines.
  • C. Reims
    Reims is a historic city in northeastern France known for its Gothic cathedral, role in French coronations, and significance during both World Wars.
  • D. Lubersac
    Lubersac is a small commune in the Corrèze department of south-central France, known for its rural character and traditional Limousin heritage.
  • E. Soissons
    Soissons is a historic town in northern France known for its strategic military importance and notable battles throughout European history.
  • 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_69d886d090cc8190a39cb94992586905 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc2906a081909d0d43cf04319f52 completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0195428c6c8190a11e3f7c8f6796fe in_progress May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:35 a.m.