Triple

T14480458
Position Surface form Disambiguated ID Type / Status
Subject Église Saint-Pierre de Tonnerre E359088 entity
Predicate locatedIn P40 FINISHED
Object Tonnerre E72887 NE FINISHED

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: Tonnerre | Statement: [Église Saint-Pierre de Tonnerre, locatedIn, Tonnerre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tonnerre
Context triple: [Église Saint-Pierre de Tonnerre, locatedIn, Tonnerre]
  • A. Tonnerre
    Tonnerre was a French warship involved in the early 19th-century naval conflict known as the Battle of the Basque Roads.
  • B. Tonnerre chosen
    Tonnerre is a historic commune in the Yonne department of Bourgogne-Franche-Comté in north-central France, known for its medieval heritage and notable residents.
  • C. Trembleur
    Trembleur is a village in the municipality of Blegny in the province of Liège, Belgium.
  • D. Durolle
    Durolle is a river in central France that flows through the town of Thiers, historically powering its renowned cutlery and knife-making industry.
  • E. Thieux
    Thieux is a small French commune located in the Seine-et-Marne department in the Île-de-France region in north-central France.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de924a576c819098351efabdb779b1 completed April 14, 2026, 7:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d8ccd608190afd23c903cd5686a completed May 8, 2026, 4:58 a.m.
Created at: April 10, 2026, 1:20 a.m.