Triple

T920150
Position Surface form Disambiguated ID Type / Status
Subject Hanshin Tigers E19863 entity
Predicate notableCulture P1579 FINISHED
Object intense media coverage in Kansai 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: intense media coverage in Kansai | Statement: [Hanshin Tigers, notableCulture, intense media coverage in Kansai]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableCulture
Context triple: [Hanshin Tigers, notableCulture, intense media coverage in Kansai]
  • A. hasCulturalSignificanceFor
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • B. notableCategory
    Indicates that an entity is recognized as notable or significant within a particular category or classification.
  • C. culturalSphere
    Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
  • D. hasCulturalSignificance chosen
    Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
  • E. culturalExport
    Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
  • 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_69a493a099788190a696d9d8408cbaf4 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b388f0bc8190a087222636135ba5 completed March 1, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69a4b2944ff88190a260be5355132ba5 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.