Triple

T15426060
Position Surface form Disambiguated ID Type / Status
Subject Collonge E369512 entity
Predicate partOf P40 FINISHED
Object Collonge-Bellerive E69502 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: Collonge-Bellerive | Statement: [Collonge, partOf, Collonge-Bellerive]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Collonge-Bellerive
Context triple: [Collonge, partOf, Collonge-Bellerive]
  • A. Collonge-Bellerive chosen
    Collonge-Bellerive is a lakeside municipality in western Switzerland known for its residential character and location on the southern shore of Lake Geneva.
  • B. Corseaux
    Corseaux is a small Swiss municipality on the shores of Lake Geneva in the canton of Vaud, known for its scenic setting and residential character.
  • C. Chens-sur-Léman
    Chens-sur-Léman is a French commune on the southern shore of Lake Geneva in the Haute-Savoie department of the Auvergne-Rhône-Alpes region.
  • D. Bardonnex
    Bardonnex is a small Swiss municipality located in the canton of Geneva, near the country’s border with France.
  • E. 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.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec1fb288190a3625b8e4f487dd1 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf0a12e081908d7d2ae7c9774f94 completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 3:20 a.m.