Triple

T17143618
Position Surface form Disambiguated ID Type / Status
Subject TGV Est E416032 entity
Predicate connectsCity P4245 FINISHED
Object Reims E9677 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: Reims | Statement: [TGV Est, connectsCity, Reims]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reims
Context triple: [TGV Est, connectsCity, Reims]
  • A. Reims chosen
    Reims is a historic city in northeastern France known for its Gothic cathedral, role in French coronations, and significance during both World Wars.
  • B. Troyes
    Troyes is a historic city in northeastern France, known for its well-preserved medieval old town, half-timbered houses, and Gothic churches.
  • C. Creil
    Creil is a commuter town in northern France’s Oise department, known as a regional rail hub connecting Paris with Picardy via major train and RER lines.
  • D. Meaux
    Meaux is a historic commune in the Île-de-France region of north-central France, known for its cathedral, World War I heritage, and production of Brie de Meaux cheese.
  • E. Amiens
    Amiens is a historic city in northern France, known for its Gothic cathedral and role as the site of the 1802 Treaty of Amiens.
  • 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f2d73c3c81908b875023bb925edb completed April 18, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0167369d9481909015c34d475fac14 completed May 11, 2026, 5:20 a.m.
Created at: April 10, 2026, 5:36 a.m.