Triple
T38079911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGA–GT rivalry |
E950821
|
entity |
| Predicate | fanTraditionsGT |
P150497
|
FINISHED |
| Object | "To Hell with Georgia" chant |
—
|
LITERAL 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: "To Hell with Georgia" chant | Statement: [UGA–GT rivalry, fanTraditionsGT, "To Hell with Georgia" chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanTraditionsGT Context triple: [UGA–GT rivalry, fanTraditionsGT, "To Hell with Georgia" chant]
-
A.
fanTraditionContext
chosen
Indicates the cultural or situational context in which a fan-related tradition occurs or is practiced.
-
B.
HallOfFameGame
Indicates that an entity is associated with participation in, or designation as, a Hall of Fame game event.
-
C.
postGameTradition
Indicates a customary activity or ritual that participants regularly engage in after a game has concluded.
-
D.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
E.
fanBase1
Indicates that one entity serves as the primary or original fan base supporting another entity.
- 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_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.