Triple

T24148688
Position Surface form Disambiguated ID Type / Status
Subject Ryōtsu E598464 entity
Predicate subdivisionTypeBeforeDissolution P155016 FINISHED
Object municipality 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: municipality | Statement: [Ryōtsu, subdivisionTypeBeforeDissolution, municipality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeBeforeDissolution
Context triple: [Ryōtsu, subdivisionTypeBeforeDissolution, municipality]
  • A. subdivisionType0
    Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
  • B. censusSubdivisionTypeBeforeMerger
    Indicates the type or classification of a census subdivision that it held prior to being merged into another administrative unit.
  • C. hasTypeOfSubdivision
    Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
  • D. subdivisionStatus
    Indicates the current state or phase of a subdivision process or classification for an entity.
  • E. traditionalSubdivisionOf
    Indicates that one entity is a historically or culturally recognized sub-unit or component region of another, according to traditional (rather than strictly modern administrative) divisions.
  • F. None of above. chosen

Provenance (4 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_69e288c9e488819093dd1acd91b08b8a completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1e00d252c8190a02bec29189baad0 completed April 29, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69f1765650fc8190a6bc1eb512b240bf completed April 29, 2026, 3:09 a.m.
PDg Predicate description generation batch_69f17c28b684819084eea522126463f8 completed April 29, 2026, 3:34 a.m.
Created at: April 17, 2026, 11:30 p.m.