Triple

T20432032
Position Surface form Disambiguated ID Type / Status
Subject Antoine Santerre E501155 entity
Predicate familyName P18 FINISHED
Object Santerre 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: Santerre | Statement: [Antoine Santerre, familyName, Santerre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santerre
Context triple: [Antoine Santerre, familyName, Santerre]
  • A. Santerre chosen
    Santerre is a French surname most notably associated with Antoine Joseph Santerre, a prominent figure of the French Revolution.
  • B. Bessières
    Bessières is a French surname most notably borne by Jean-Baptiste Bessières, a Marshal of the Empire under Napoleon.
  • C. Bessières
    Bessières is a metro station on the Lausanne Métro network in Lausanne, Switzerland.
  • D. Roquebillière
    Roquebillière is a small commune in southeastern France, situated in the Alpes-Maritimes department in the Provence-Alpes-Côte d’Azur region.
  • E. Mouriès
    Mouriès is a village in southern France’s Provence region, known for its olive oil production and location near the Alpilles hills.
  • 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_69e0b4ab3cfc8190ac9bf32e932316b1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e685eaa4c8819083d1d7aee0f998a6 completed April 20, 2026, 8 p.m.
Created at: April 16, 2026, 11:31 a.m.