Triple

T19877241
Position Surface form Disambiguated ID Type / Status
Subject Rüti ZH E477669 entity
Predicate hasMunicipalityCodeSystem P116809 FINISHED
Object Swiss municipality code system LITERAL 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: Swiss municipality code system | Statement: [Rüti ZH, hasMunicipalityCodeSystem, Swiss municipality code system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMunicipalityCodeSystem
Context triple: [Rüti ZH, hasMunicipalityCodeSystem, Swiss municipality code system]
  • A. hasMunicipalityCode
    Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
  • B. municipalCodeSystem chosen
    Indicates a system that defines, organizes, or standardizes codes or regulations used by a municipality.
  • C. hasMunicipalityType
    Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
  • D. hasMunicipalDistrictNumber
    Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
  • E. isInMunicipality
    Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
  • F. None of above.

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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658dbdb648190b423865e7994a8fe completed April 20, 2026, 4:48 p.m.
PD Predicate disambiguation batch_69e537e8c4e481909fe95d795b4864e7 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:52 p.m.