Triple

T2349774
Position Surface form Disambiguated ID Type / Status
Subject Indy Eleven E47418 entity
Predicate fandomBase P38667 FINISHED
Object Indiana soccer fans 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: Indiana soccer fans | Statement: [Indy Eleven, fandomBase, Indiana soccer fans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fandomBase
Context triple: [Indy Eleven, fandomBase, Indiana soccer fans]
  • A. fandomFocus
    Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
  • B. fandomCulture
    Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
  • C. fanCultureElement
    Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
  • D. fandomNickname
    Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
  • E. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other 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_69a88a1b678c8190bce986922ba60ce0 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abcb802da08190980100444010f91e completed March 7, 2026, 6:53 a.m.
PD Predicate disambiguation batch_69abc5981ce48190a3f7852d28276e11 completed March 7, 2026, 6:28 a.m.
PDg Predicate description generation batch_69abcb7ebb708190ba7edffee3c45d8b completed March 7, 2026, 6:53 a.m.
Created at: March 4, 2026, 7:54 p.m.