Triple

T3911335
Position Surface form Disambiguated ID Type / Status
Subject Beppu E87326 entity
Predicate localGovernmentForm P12191 FINISHED
Object mayor–council system 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: mayor–council system | Statement: [Beppu, localGovernmentForm, mayor–council system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localGovernmentForm
Context triple: [Beppu, localGovernmentForm, mayor–council system]
  • A. governmentFormCreated
    Indicates that one entity established or instituted a particular form or system of government for another entity.
  • B. governmentFormDefined
    Indicates that the specific form or structure of governance for an entity has been formally specified or classified.
  • C. mayorCouncilForm chosen
    Indicates that a municipality operates under a mayor–council form of government, where executive authority is vested in an elected mayor and legislative authority in an elected council.
  • D. countyGovernment
    Indicates that a county-level governmental authority has jurisdiction over, administers, or is responsible for the referenced entity.
  • E. governmentFormProposed
    Indicates that a particular form or structure of government has been put forward as a proposal by an 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_69aed9424514819086e9c58adde6652d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef1abe2dc81909c18aeae9b286898 completed March 9, 2026, 4:13 p.m.
PD Predicate disambiguation batch_69aee75cff148190b6d5979d17fae085 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:22 p.m.