Triple
T28870293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucknell University Bison athletics program |
E732123
|
entity |
| Predicate | sponsorOfSport |
P790
|
FINISHED |
| Object | men's basketball |
—
|
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: men's basketball | Statement: [Bucknell University Bison athletics program, sponsorOfSport, men's basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorOfSport Context triple: [Bucknell University Bison athletics program, sponsorOfSport, men's basketball]
-
A.
sponsorSport
chosen
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
B.
alsoSponsorsSport
Indicates that an entity that sponsors one sport also sponsors another sport.
-
C.
sportsSponsored
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
D.
sponsorOfStadiumName
Indicates that an entity serves as the naming-rights sponsor for a particular stadium.
-
E.
sponsorField
Indicates that one entity acts as a sponsor specifically in the context of a particular field, domain, or area associated with another entity.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:31 a.m.