Triple
T38080080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Auburn football rivalry |
E950827
|
entity |
| Predicate | homeStadiumAuburn |
P189989
|
FINISHED |
| Object | Jordan–Hare 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: Jordan–Hare Stadium | Statement: [Georgia vs. Auburn football rivalry, homeStadiumAuburn, Jordan–Hare Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumAuburn Context triple: [Georgia vs. Auburn football rivalry, homeStadiumAuburn, Jordan–Hare Stadium]
-
A.
AuburnRecordBeforeGame
Indicates that the predicate relates to Auburn’s performance record (such as wins and losses) as it stood prior to a specific game.
-
B.
TennesseeHomeStadium
Indicates that a given stadium serves as the home stadium for a Tennessee-based sports team or organization.
-
C.
AuburnQuarterback
Indicates that the subject serves as or is identified as the quarterback for Auburn University's football team.
-
D.
BCSRankingOfAuburnBeforeGame
Indicates the position Auburn held in the BCS rankings prior to a specific game.
-
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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.