Triple

T26900844
Position Surface form Disambiguated ID Type / Status
Subject Yagi E678023 entity
Predicate municipalMergerWith P80558 FINISHED
Object Miyama 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: Miyama | Statement: [Yagi, municipalMergerWith, Miyama]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalMergerWith
Context triple: [Yagi, municipalMergerWith, Miyama]
  • A. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • B. incorporatedAsMunicipalityBy
    Indicates that an entity was formally established and given municipal status through official action by another governing body or authority.
  • C. formerMunicipalityDisestablished
    Indicates that a municipality, which previously existed as an administrative unit, was officially dissolved or ceased to exist at a specific point in time.
  • D. hasMunicipalConsolidationWith chosen
    Indicates that two or more municipalities have been officially merged or unified into a single administrative entity or structure.
  • E. formerCivilParishMergedInto
    Indicates that a former civil parish has been administratively combined into another civil parish or local government unit, ceasing to exist as a separate entity.
  • 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_69eee9befee48190a26f214faa867be7 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6352fdb788190b9bad30243690743 completed May 2, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69f631850ae08190a0ba51e4f1e4ccb3 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 5:50 a.m.