Triple

T30785695
Position Surface form Disambiguated ID Type / Status
Subject メタボリズム E783948 entity
Predicate 地理的中心 P1822 FINISHED
Object 東京 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: 東京 | Statement: [メタボリズム, 地理的中心, 東京]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 地理的中心
Context triple: [メタボリズム, 地理的中心, 東京]
  • A. geographicCenter chosen
    Indicates the location that serves as the central point of a geographic area or region.
  • B. geographicRole
    Indicates a relationship where one entity serves a specific geographic function, status, or role in relation to another location or area.
  • C. geographicalStructure
    Indicates a relationship where one entity is a physical geographic feature or formation that characterizes or shapes the spatial nature of another entity or area.
  • D. geographicContext
    Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
  • E. isGeographicalEntity
    Indicates that something exists as a distinct geographic feature, area, or place within physical space.
  • 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_69f224b213c8819083886073f90b647e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68fe8168c8190b083be0e33988b9c completed May 2, 2026, 11:59 p.m.
PD Predicate disambiguation batch_69f686140aa08190a35f62572b2db9b6 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:41 p.m.