Triple

T927930
Position Surface form Disambiguated ID Type / Status
Subject Hankyu Hanshin Holdings, Inc. E20025 entity
Predicate regionSpecialization P21480 FINISHED
Object Kansai private railway sector 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: Kansai private railway sector | Statement: [Hankyu Hanshin Holdings, Inc., regionSpecialization, Kansai private railway sector]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionSpecialization
Context triple: [Hankyu Hanshin Holdings, Inc., regionSpecialization, Kansai private railway sector]
  • A. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • B. regionSpecificContent
    Indicates that certain content is tailored, restricted, or applicable only to a particular geographic region or set of regions.
  • C. regionType
    Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
  • D. regionRuled
    Indicates that a particular region is governed or controlled by a specified ruler or authority.
  • E. regionCoverage
    Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
  • F. None of above. chosen

Provenance (4 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_69a493af3dc48190adb7263e6e445ea1 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b32de3cc81908a0ef885795677ff completed March 1, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69a4b29876348190a29f4ff9878074a5 completed March 1, 2026, 9:41 p.m.
PDg Predicate description generation batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 completed March 1, 2026, 9:43 p.m.
Created at: March 1, 2026, 7:40 p.m.