Triple

T16227664
Position Surface form Disambiguated ID Type / Status
Subject Taihaku-ku E393894 entity
Predicate hasMunicipalStatusAsOf P37705 FINISHED
Object 1989 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: 1989 | Statement: [Taihaku-ku, hasMunicipalStatusAsOf, 1989]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMunicipalStatusAsOf
Context triple: [Taihaku-ku, hasMunicipalStatusAsOf, 1989]
  • A. hasMunicipalStatusUntil
    Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
  • B. isMunicipalStatus chosen
    Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
  • C. hasMunicipalStatusChange
    Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
  • D. hasLocalGovernmentStatusSinceCountryFormation
    Indicates that an entity has held local government status continuously since the time its country was formed.
  • E. hasMunicipalFormation
    Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e23d2785f88190ae80d5d61129d3e5 completed April 17, 2026, 2:01 p.m.
PD Predicate disambiguation batch_69e219e94a448190b73a4e6aa374eb4a completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:03 a.m.