Triple
T29296786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illibuck Trophy |
E742853
|
entity |
| Predicate | homeStadiumWhenIllinoisHosts |
P168138
|
FINISHED |
| Object | Memorial Stadium (Champaign) |
—
|
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: Memorial Stadium (Champaign) | Statement: [Illibuck Trophy, homeStadiumWhenIllinoisHosts, Memorial Stadium (Champaign)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumWhenIllinoisHosts Context triple: [Illibuck Trophy, homeStadiumWhenIllinoisHosts, Memorial Stadium (Champaign)]
-
A.
homeStadiumInvolved
Indicates that an event, action, or relationship involves a team's home stadium as a relevant location or context.
-
B.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
C.
homeStadiumLocatedIn
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
-
D.
homeStadiumTeam
Indicates that a particular stadium serves as the designated home venue for a specific sports team.
-
E.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
- F. None of above. chosen
Provenance (4 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 1:07 p.m.