Triple

T18162199
Position Surface form Disambiguated ID Type / Status
Subject Battle of Héricourt E434792 entity
Predicate place P373 FINISHED
Object Héricourt 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: Héricourt | Statement: [Battle of Héricourt, place, Héricourt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Héricourt
Context triple: [Battle of Héricourt, place, Héricourt]
  • A. Héricourt chosen
    Héricourt is a commune in eastern France known for its historical architecture and location within the Bourgogne-Franche-Comté region.
  • B. Bessancourt
    Bessancourt is a small suburban commune in the Val-d'Oise department in the Île-de-France region of northern France, forming part of the northwestern outskirts of Paris.
  • C. Rachecourt
    Rachecourt is a village in the municipality of Aubange in the province of Luxembourg, Belgium.
  • D. Levécourt
    Levécourt is a small French village historically notable as the birthplace of the renowned 17th-century bellfounder Pieter Hemony.
  • E. Bellecourt
    Bellecourt is a surname most notably associated with Native American activist Vernon Bellecourt.
  • 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec32530819099d906640a07e92c completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 10:30 a.m.