Triple

T18383624
Position Surface form Disambiguated ID Type / Status
Subject Seligenstadt E446520 entity
Predicate twinTown P1072 FINISHED
Object Triel-sur-Seine 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: Triel-sur-Seine | Statement: [Seligenstadt, twinTown, Triel-sur-Seine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Triel-sur-Seine
Context triple: [Seligenstadt, twinTown, Triel-sur-Seine]
  • A. Triel-sur-Seine chosen
    Triel-sur-Seine is a commune in the Yvelines department of north-central France, situated along the Seine River to the northwest of Paris.
  • B. Tournus
    Tournus is a historic town in eastern France’s Burgundy region, known for its Romanesque abbey and riverside setting along the Saône.
  • C. Essonnes
    Essonnes was a former commune in northern France that later became part of the town of Corbeil-Essonnes in the Île-de-France region.
  • D. Gonesse
    Gonesse is a commune in the northeastern suburbs of Paris, France, known historically as a rural town and now as part of the greater Paris metropolitan area.
  • E. Meyriez
    Meyriez is a small municipality in the canton of Fribourg in western Switzerland, situated on the shores of Lake Murten.
  • 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e5179da1048190944398e229e7a4c1 completed April 19, 2026, 5:57 p.m.
Created at: April 10, 2026, 10:45 a.m.