Triple
T33786463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UB Stadium |
E865800
|
entity |
| Predicate | isPrimaryFootballStadiumFor |
P70079
|
FINISHED |
| Object | University at Buffalo |
—
|
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: University at Buffalo | Statement: [UB Stadium, isPrimaryFootballStadiumFor, University at Buffalo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryFootballStadiumFor Context triple: [UB Stadium, isPrimaryFootballStadiumFor, University at Buffalo]
-
A.
isLocalStadiumFor
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
-
B.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
C.
stadiumFor
chosen
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
D.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
-
E.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 1:45 a.m.