Triple

T35300980
Position Surface form Disambiguated ID Type / Status
Subject Million Pound Game E1019502 entity
Predicate hasFanImpact P191019 FINISHED
Object high emotional investment from supporters 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: high emotional investment from supporters | Statement: [Million Pound Game, hasFanImpact, high emotional investment from supporters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanImpact
Context triple: [Million Pound Game, hasFanImpact, high emotional investment from supporters]
  • A. hasFandomImpact chosen
    Indicates that something significantly influences, shapes, or contributes to the behavior, culture, or development of a fan community.
  • B. hasFan
    Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
  • C. hasSignificantInfluenceIn
    Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
  • D. hasFanActivity
    Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
  • E. hasImpactFocus
    Indicates that an entity is primarily concerned with or directed toward a particular type or area of impact.
  • 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_69f76de8b4c48190ae504b86185c474c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fddf721c1481909301a0f379368f10 completed May 8, 2026, 1:04 p.m.
PD Predicate disambiguation batch_69fddda1ae7c8190b5848ff9a9e39826 completed May 8, 2026, 12:57 p.m.
Created at: May 3, 2026, 4:03 p.m.