Triple

T33090654
Position Surface form Disambiguated ID Type / Status
Subject Kids Heart Challenge E846770 entity
Predicate replaced P101 FINISHED
Object Hoops For Heart
Hoops For Heart was a school-based American Heart Association program that promoted physical activity and heart health through basketball-themed fundraising events.
E2035959 NE 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: Hoops For Heart | Statement: [Kids Heart Challenge, replaced, Hoops For Heart]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hoops For Heart
Triple: [Kids Heart Challenge, replaced, Hoops For Heart]
Generated description
Hoops For Heart was a school-based American Heart Association program that promoted physical activity and heart health through basketball-themed fundraising events.

Provenance (5 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_69f3495590dc8190aa04f3dec74ce976 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d625dd608190bce1a80c7c30d2b4 completed May 3, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34f026c81481909a6e49f03dde90c6 completed June 19, 2026, 7:30 a.m.
NEDg Description generation batch_6a34ffda4924819095b4a76ed9e5a3c3 completed June 19, 2026, 8:37 a.m.
NED2 Entity disambiguation (via description) batch_6a3500be2b44819089b389b1843bf4d1 completed June 19, 2026, 8:41 a.m.
Created at: May 1, 2026, 1:26 a.m.