Triple

T14550970
Position Surface form Disambiguated ID Type / Status
Subject Conseil municipal de Lancy E341415 entity
Predicate jurisdiction P82 FINISHED
Object commune de Lancy E68579 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: commune de Lancy | Statement: [Conseil municipal de Lancy, jurisdiction, commune de Lancy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: commune de Lancy
Context triple: [Conseil municipal de Lancy, jurisdiction, commune de Lancy]
  • A. Lancy chosen
    Lancy is a suburban municipality in western Switzerland that forms part of the urban area of Geneva.
  • B. Lussy
    Lussy is a small municipality in the Glâne District of the canton of Fribourg in western Switzerland.
  • C. Commune of Rolle
    The Commune of Rolle is a Swiss municipality on the shores of Lake Geneva, known for its historic lakeside town, wine-growing region, and picturesque setting between Lausanne and Geneva.
  • D. Commune d’Onex
    The Commune d’Onex is the municipal authority responsible for governing the town of Onex in the canton of Geneva, Switzerland.
  • E. Lully (Fribourg)
    Lully (Fribourg) is a small municipality in the canton of Fribourg in western Switzerland.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2ee34208190bf040a513767c958 completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8ab5d50881908f53f8b7539c6fde completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.