Triple

T14723530
Position Surface form Disambiguated ID Type / Status
Subject Sablé-sur-Sarthe E345875 entity
Predicate hasRailConnectionTo P848 FINISHED
Object Le Mans E43233 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: Le Mans | Statement: [Sablé-sur-Sarthe, hasRailConnectionTo, Le Mans]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Le Mans
Context triple: [Sablé-sur-Sarthe, hasRailConnectionTo, Le Mans]
  • A. Le Mans chosen
    Le Mans is a historic city in northwestern France best known for its annual 24 Hours of Le Mans endurance sports car race.
  • B. Montlhéry
    Montlhéry is a commune in northern France best known for its historic motor racing circuit, the Autodrome de Linas-Montlhéry.
  • C. Viroflay
    Viroflay is a suburban commune in the Yvelines department of the Île-de-France region in north-central France, located just southwest of Paris.
  • D. Deauzya
    Deauzya is the given first name of American professional basketball player DiDi Richards.
  • E. Arques
    Arques is a river in northern France that flows through the Normandy region and reaches the English Channel at the port city of Dieppe.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec25e9a14819081fa06fc601f295d completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf09791e081908a1262717fd31445 completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:29 a.m.