Triple

T4961390
Position Surface form Disambiguated ID Type / Status
Subject Lyon metropolitan area E111415 entity
Predicate containsCity P294 FINISHED
Object Villeurbanne E96069 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: Villeurbanne | Statement: [Lyon metropolitan area, containsCity, Villeurbanne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Villeurbanne
Context triple: [Lyon metropolitan area, containsCity, Villeurbanne]
  • A. Villeurbanne chosen
    Villeurbanne is a major suburban city adjacent to Lyon in eastern France, known for its dense urban character and role as part of the Lyon metropolitan area.
  • B. Saint-Priest
    Saint-Priest is a suburban commune in eastern France that forms part of the metropolitan area of Lyon.
  • C. 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.
  • D. Boulogne-Billancourt
    Boulogne-Billancourt is a densely populated suburban city just southwest of central Paris, known as a major economic and media hub in the Île-de-France region.
  • E. Meyzieu
    Meyzieu is a suburban commune in eastern France, located near Lyon and known for its residential character and proximity to major transport links.
  • 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_69bd4419393c819086319a6fe4bf8542 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd71dc06a48190827d54a5c0351aab completed March 20, 2026, 4:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf486d43488190b57e064b0272ece4 completed March 22, 2026, 1:39 a.m.
Created at: March 20, 2026, 1:32 p.m.