Triple

T6662939
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Metropolitan Assembly E151520 entity
Predicate instanceOf P0 FINISHED
Object regional assembly C21157 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: regional assembly
Context triple: [Tokyo Metropolitan Assembly, instanceOf, regional assembly]
  • A. planned regional parliament
    A planned regional parliament is a proposed legislative body intended to represent and govern a specific geographic region, but which has not yet been formally established or begun operation.
  • B. regional forum
    A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
  • C. regional organisation of councils
    A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
  • D. regional division
    A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
  • E. regional administrative branch
    A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
  • F. None of above. chosen

Provenance (1 batch)

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_69c687f5fac48190a09e4838d9c6b45d completed March 27, 2026, 1:36 p.m.
Created at: March 27, 2026, 2:02 p.m.