Triple

T1503066
Position Surface form Disambiguated ID Type / Status
Subject Garden State Ultras E33838 entity
Predicate fanCultureType P16083 FINISHED
Object ultras 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: ultras | Statement: [Garden State Ultras, fanCultureType, ultras]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fanCultureType
Context triple: [Garden State Ultras, fanCultureType, ultras]
  • A. fanCultureElement
    Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
  • B. fandomCulture chosen
    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. fandomFocus
    Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
  • D. inFilmAndTV
    Indicates that the subject appears or is featured within the context of film and television works.
  • E. notableCultTitle
    Indicates that an entity holds a title or designation that is especially prominent or significant within a particular cult or cult-like group.
  • 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_69a885f352a4819099b24ff15489dede completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90584b8b881908e112c7e59163812 completed March 5, 2026, 4:24 a.m.
PD Predicate disambiguation batch_69a88727ce48819089b482cdc25453d1 completed March 4, 2026, 7:25 p.m.
Created at: March 4, 2026, 7:24 p.m.