Triple
T28968505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn State–Michigan State football rivalry |
E732106
|
entity |
| Predicate | homeStadiumPennState |
P166519
|
FINISHED |
| Object | Beaver 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: Beaver Stadium | Statement: [Penn State–Michigan State football rivalry, homeStadiumPennState, Beaver Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumPennState Context triple: [Penn State–Michigan State football rivalry, homeStadiumPennState, Beaver Stadium]
-
A.
teamNicknamePennState
Indicates that the object is a nickname used for the sports teams representing Penn State University.
-
B.
homeArenaOfPenn
Indicates that one entity is the home arena or primary venue used by the Penn team or organization.
-
C.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
D.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
E.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 8:53 a.m.