Triple
T29037723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Bowl Association |
E737909
|
entity |
| Predicate | homeStadiumUsedForEvent |
P167395
|
FINISHED |
| Object | Raymond James Stadium |
—
|
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: Raymond James Stadium | Statement: [Tampa Bay Bowl Association, homeStadiumUsedForEvent, Raymond James Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumUsedForEvent Context triple: [Tampa Bay Bowl Association, homeStadiumUsedForEvent, Raymond James Stadium]
-
A.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
homeTeamStadiumUsed
Indicates that a particular stadium is used as the home venue by a specified home team.
-
C.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
D.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 9:59 a.m.