Triple

T30861368
Position Surface form Disambiguated ID Type / Status
Subject 高松シンボルタワー E786068 entity
Predicate 地域の役割 P12921 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. 地域的役割
    Indicates that something has a specific function, responsibility, or role within a particular region or locality.
  • B. geographicRole
    Indicates a relationship where one entity serves a specific geographic function, status, or role in relation to another location or area.
  • C. ethnicRole
    Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
  • D. hasRegionalRole chosen
    Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
  • E. roleInAdministrativeDivision
    Indicates that an entity holds or fulfills a specific role, function, or position within a particular administrative division or jurisdiction.
  • 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_69f224b91c14819084e764832fe67a57 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f691a92b6081909e009d05ee9023b2 completed May 3, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:47 p.m.