Triple

T23660206
Position Surface form Disambiguated ID Type / Status
Subject Peseux E584421 entity
Predicate hasFormerMunicipalityStatusIn P113812 FINISHED
Object canton of Neuchâtel 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: canton of Neuchâtel | Statement: [Peseux, hasFormerMunicipalityStatusIn, canton of Neuchâtel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFormerMunicipalityStatusIn
Context triple: [Peseux, hasFormerMunicipalityStatusIn, canton of Neuchâtel]
  • A. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • B. hasVoivodeshipStatusInPast
    Indicates that an entity previously held the status of a voivodeship (administrative region) but no longer does so.
  • C. previousMunicipalityStatus
    Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
  • D. wasMunicipalityIn chosen
    Indicates that an entity previously held the status of a municipality within a specified administrative or territorial unit.
  • E. hasFormerCounty
    Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
  • 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_69e248ffc0888190ae23c4731eb8b7ac completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b35f03448190834991c2a65ef0e4 completed April 29, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69f118d7903c8190bb590a71771e93af completed April 28, 2026, 8:30 p.m.
Created at: April 17, 2026, 6:50 p.m.