Triple

T36065277
Position Surface form Disambiguated ID Type / Status
Subject Shizunai E1043207 entity
Predicate hasSubprefectureCapitalRole P94831 FINISHED
Object Hidaka Subprefecture 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: Hidaka Subprefecture | Statement: [Shizunai, hasSubprefectureCapitalRole, Hidaka Subprefecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSubprefectureCapitalRole
Context triple: [Shizunai, hasSubprefectureCapitalRole, Hidaka Subprefecture]
  • A. subprefectureCapital chosen
    Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
  • B. subprefectureOf
    Indicates that one administrative subprefecture is a subordinate division within and officially belongs to a larger governing region or prefecture.
  • C. hasPrefecturalCapitalFunction
    Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
  • D. belongsToPrefecturalCapitalArea
    Indicates that a given place is part of, or administratively associated with, the surrounding area of a prefectural capital.
  • E. isInPrefecturalCapital
    Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
  • 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_69f76e2fd3248190b900d9a492bf5a7a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a000a1d8fa88190a1d82ac746565c48 completed May 10, 2026, 4:31 a.m.
PD Predicate disambiguation batch_6a0008b26eb88190ae03b2309a614774 completed May 10, 2026, 4:25 a.m.
Created at: May 3, 2026, 4:08 p.m.