Triple

T19677082
Position Surface form Disambiguated ID Type / Status
Subject arrondissement of Grenoble E472479 entity
Predicate contains P35 FINISHED
Object Voiron 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: Voiron | Statement: [arrondissement of Grenoble, contains, Voiron]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Voiron
Context triple: [arrondissement of Grenoble, contains, Voiron]
  • A. Voiron chosen
    Voiron is a commune in southeastern France known for its historical town center and proximity to the Chartreuse Mountains.
  • B. Chassieu
    Chassieu is a commune in the Metropolis of Lyon in eastern France, known for its residential areas and proximity to the Lyon urban center.
  • C. Saint-Véran
    Saint-Véran is a French wine appellation in southern Burgundy known for its high-quality Chardonnay-based white wines.
  • D. Gueugnon
    Gueugnon is a small commune in eastern France known historically for its steel industry and location in the Bourgogne-Franche-Comté region.
  • E. Brioude
    Brioude is a historic town in south-central France known for its Romanesque Basilica of Saint-Julien and its location in the Haute-Loire department of the Auvergne region.
  • 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e641bceef881909c5b655af709c8c6 completed April 20, 2026, 3:09 p.m.
Created at: April 10, 2026, 1:45 p.m.