Triple

T10744304
Position Surface form Disambiguated ID Type / Status
Subject Southern Professional Hockey League E253410 entity
Predicate hasFanBaseType P95750 FINISHED
Object local community-oriented fan bases 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: local community-oriented fan bases | Statement: [Southern Professional Hockey League, hasFanBaseType, local community-oriented fan bases]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanBaseType
Context triple: [Southern Professional Hockey League, hasFanBaseType, local community-oriented fan bases]
  • A. hasFanBaseFrom
    Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
  • B. hasFanBaseTension
    Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
  • C. hasFan
    Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
  • D. hasBaseField
    Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
  • E. hasSupportBaseIn
    Indicates that one entity maintains an operational or organizational base of support located in 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_69d6aa5e51e8819095f06881cecf152e completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d711b6b4b48190bad08500fa963062 completed April 9, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69d6f30df9948190ab3cdc33977fac14 completed April 9, 2026, 12:30 a.m.
PDg Predicate description generation batch_69d6fa323564819097b207eb53f8a9b8 completed April 9, 2026, 1 a.m.
Created at: April 8, 2026, 9:15 p.m.