Triple
T25988623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XL Center as primary home for UConn hockey |
E646275
|
entity |
| Predicate | associatedAthleticsBrand |
P5816
|
FINISHED |
| Object | UConn Huskies |
—
|
NE NERFINISHED |
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: UConn Huskies | Statement: [XL Center as primary home for UConn hockey, associatedAthleticsBrand, UConn Huskies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAthleticsBrand Context triple: [XL Center as primary home for UConn hockey, associatedAthleticsBrand, UConn Huskies]
-
A.
sportsBrand
chosen
Indicates that one entity is a sports-related brand or label associated with the other entity.
-
B.
formerAthleticBrand
Indicates that an entity previously served as an athletic brand for another entity but no longer holds that status.
-
C.
sportsAuthority
Indicates that one entity holds official power, control, or governance over sports-related activities, organizations, or regulations in relation to another entity.
-
D.
competitionBrand
Indicates that one brand is a competitor of another brand in the same or overlapping market.
-
E.
playersClubBrand
Indicates that a player is associated with or represents a particular club’s brand.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 22, 2026, 8:55 a.m.