Triple
T38079799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia–Georgia Tech football rivalry |
E950819
|
entity |
| Predicate | cityOfGeorgiaTechHomeGames |
P175826
|
FINISHED |
| Object | Atlanta, Georgia |
—
|
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: Atlanta, Georgia | Statement: [Georgia–Georgia Tech football rivalry, cityOfGeorgiaTechHomeGames, Atlanta, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfGeorgiaTechHomeGames Context triple: [Georgia–Georgia Tech football rivalry, cityOfGeorgiaTechHomeGames, Atlanta, Georgia]
-
A.
cityGeorgiaHomeGames
Indicates that the referenced games are home games played in the city located in the state of Georgia.
-
B.
homeCityOfRivalryGames
chosen
Indicates that a city is the primary home location where a pair of rival teams regularly play their rivalry games.
-
C.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
D.
homeTeamUniversity
Indicates that a specified university serves as the home institution or host team in a given game, match, or sporting event.
-
E.
cityOhioStateHomeGames
Indicates that a city in Ohio is the location where a team plays its home games.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:21 p.m.