Triple

T12083004
Position Surface form Disambiguated ID Type / Status
Subject Armançon E287728 entity
Predicate flowsThrough P225 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: [Armançon, flowsThrough, Tonnerre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tonnerre
Context triple: [Armançon, flowsThrough, Tonnerre]
  • A. 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.
  • B. Durolle
    Durolle is a river in central France that flows through the town of Thiers, historically powering its renowned cutlery and knife-making industry.
  • C. Thieux
    Thieux is a small French commune located in the Seine-et-Marne department in the Île-de-France region in north-central France.
  • D. Blera
    Blera is a small historic town in the Lazio region of central Italy, known for its ancient Etruscan origins and medieval heritage.
  • E. Valleiry
    Valleiry is a small French commune in the Haute-Savoie department of the Auvergne-Rhône-Alpes region in southeastern France, near the Swiss border.
  • 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_69d6ab4964708190850585628b287b0c completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915124e4c8190b0264c2a09e3c2f3 completed April 10, 2026, 3:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f66509208190b7206e78df41c2fe completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.