Triple

T27037996
Position Surface form Disambiguated ID Type / Status
Subject Baník Ostrava E681107 entity
Predicate homeRegionSupport P161792 FINISHED
Object strong support in Ostrava and surrounding areas 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: strong support in Ostrava and surrounding areas | Statement: [Baník Ostrava, homeRegionSupport, strong support in Ostrava and surrounding areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homeRegionSupport
Context triple: [Baník Ostrava, homeRegionSupport, strong support in Ostrava and surrounding areas]
  • A. supportsRegion
    Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
  • B. issuerRegionServed
    Indicates the geographic region or area that the issuer provides services to or operates within.
  • C. hasRegionalServices
    Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
  • D. supportsRegionRestriction
    Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
  • E. serviceRegion
    Indicates the geographic area or jurisdiction within which a service is provided or applicable.
  • 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_69eeeb5566f08190813daf896fa3da04 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f62269df6881908d2b4648e4b67ced completed May 2, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69f61b3ee7b08190a0a1bc5d26b757aa completed May 2, 2026, 3:41 p.m.
PDg Predicate description generation batch_69f61f109ef48190873bfe18638d2046 completed May 2, 2026, 3:58 p.m.
Created at: April 27, 2026, 7:17 a.m.