Triple

T23156536
Position Surface form Disambiguated ID Type / Status
Subject Saint-Pierre E578453 entity
Predicate municipalStatusRestored P130645 FINISHED
Object 1923 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: 1923 | Statement: [Saint-Pierre, municipalStatusRestored, 1923]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalStatusRestored
Context triple: [Saint-Pierre, municipalStatusRestored, 1923]
  • A. previousMunicipalityStatus
    Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
  • B. isMunicipalStatus
    Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
  • C. recoveredTownStatusIn
    Indicates that an entity has regained its status as a town within a specified jurisdiction or time period.
  • D. hasMunicipalStatusChange
    Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
  • E. reconstitutedAsMunicipality chosen
    Indicates that an entity which previously lost or changed its municipal status has been formally re-established or reorganized as a 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18efd598c81908fba9d583e30660e completed April 29, 2026, 4:54 a.m.
PD Predicate disambiguation batch_69ef89ff76808190808ee4ad9dea776b completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4:01 p.m.