Triple

T38215
Position Surface form Disambiguated ID Type / Status
Subject Osaka Prefecture E757 entity
Predicate hasGovernmentForm P220 FINISHED
Object prefectural government 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: prefectural government | Statement: [Osaka Prefecture, hasGovernmentForm, prefectural government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGovernmentForm
Context triple: [Osaka Prefecture, hasGovernmentForm, prefectural government]
  • A. governmentType chosen
    Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
  • B. hasPolity
    Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
  • C. legalForm
    Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
  • D. levelOfGovernment
    Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
  • E. hasForm
    Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
  • 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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24b4d5bd08190a3a48eb26e67768c completed Feb. 28, 2026, 1:56 a.m.
PD Predicate disambiguation batch_69a24ab6141881908701106aa97e4735 completed Feb. 28, 2026, 1:53 a.m.
Created at: Feb. 28, 2026, 1:46 a.m.