Triple

T12735640
Position Surface form Disambiguated ID Type / Status
Subject We Are Family E304354 entity
Predicate continuedPopularity P57498 FINISHED
Object frequently played at sporting events 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: frequently played at sporting events | Statement: [We Are Family, continuedPopularity, frequently played at sporting events]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: continuedPopularity
Context triple: [We Are Family, continuedPopularity, frequently played at sporting events]
  • A. popularity
    Indicates how widely liked, admired, or favored something or someone is by a group of people.
  • B. popularityResurgence
    Indicates a renewed increase in attention, favor, or widespread appeal for something after a period of decline or obscurity.
  • C. hasEnduringPopularityOn chosen
    Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
  • D. popularityContext
    Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
  • E. popularInPeriod
    Indicates that something is widely liked, used, or influential during a specified time period.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69d96403957c81909acdee7bdae71696 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:26 p.m.