Triple
T38079892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGA–GT rivalry |
E950821
|
entity |
| Predicate | primaryHomeStadiumGT |
P890
|
FINISHED |
| Object | Bobby Dodd Stadium |
E548686
|
NE FINISHED |
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: Bobby Dodd Stadium | Statement: [UGA–GT rivalry, primaryHomeStadiumGT, Bobby Dodd Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHomeStadiumGT Context triple: [UGA–GT rivalry, primaryHomeStadiumGT, Bobby Dodd Stadium]
-
A.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
-
B.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
C.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
D.
homeStadium
chosen
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
E.
homeStadiumType
Indicates the type or classification of a venue that serves as a team's primary home stadium.
- F. None of above.
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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417117f5c0819087aae78cdaeb6a81 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.