Triple
T28968506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn State–Michigan State football rivalry |
E732106
|
entity |
| Predicate | homeStadiumMichiganState |
P166902
|
FINISHED |
| Object | Spartan 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: Spartan Stadium | Statement: [Penn State–Michigan State football rivalry, homeStadiumMichiganState, Spartan Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumMichiganState Context triple: [Penn State–Michigan State football rivalry, homeStadiumMichiganState, Spartan Stadium]
-
A.
cityOfMichiganStateHomeGames
Indicates that the referenced city is the location where Michigan State plays its home games.
-
B.
teamNicknameMichiganState
Indicates that a given nickname is used as the team nickname for Michigan State.
-
C.
cityOfMichiganHomeGames
Indicates the city where the University of Michigan’s home games are played.
-
D.
Michigan StateScore
Indicates that a specified score is associated with Michigan State in a particular game or event.
-
E.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
- 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_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 8:53 a.m.