Triple

T15831208
Position Surface form Disambiguated ID Type / Status
Subject Lyon bus network E383874 entity
Predicate hasServiceArea P82 FINISHED
Object Saint-Priest 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: Saint-Priest | Statement: [Lyon bus network, hasServiceArea, Saint-Priest]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saint-Priest
Context triple: [Lyon bus network, hasServiceArea, Saint-Priest]
  • A. Saint-Priest chosen
    Saint-Priest is a suburban commune in eastern France that forms part of the metropolitan area of Lyon.
  • B. Firminy
    Firminy is a commune in central France known for its notable modernist architecture, including works by Le Corbusier such as the Maison de la Culture.
  • C. Meyzieu
    Meyzieu is a suburban commune in eastern France, located near Lyon and known for its residential character and proximity to major transport links.
  • D. Bourganeuf
    Bourganeuf is a historic commune in central France’s Creuse department, known for its medieval architecture and the 15th-century Zizim Tower.
  • E. Vaulx-en-Velin
    Vaulx-en-Velin is a suburban commune in eastern France located just northeast of Lyon, known for its large housing estates and diverse population.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e11e6433ac8190a3d3e0d573673ea3 completed April 16, 2026, 5:37 p.m.
Created at: April 10, 2026, 4:49 a.m.