Triple
T38079826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-state rivalry |
C46781
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: in-state rivalry Context triple: [Georgia vs. Georgia Tech, instanceOf, in-state rivalry]
-
A.
intra-state rivalry
Intra-state rivalry is a sustained, competitive relationship between distinct political, social, or armed actors operating within the same state who contest authority, resources, or legitimacy.
-
B.
regional rivalry
Regional rivalry is a competitive and often tense relationship between neighboring areas or countries, driven by historical, cultural, economic, or political differences as they vie for influence, resources, or prestige.
-
C.
NCAA rivalry
chosen
An NCAA rivalry is a recurring, highly competitive athletic contest between two college or university programs, often fueled by historical, geographic, or cultural tensions and traditions.
-
D.
sports rivalry
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
E.
intercollegiate competition
An intercollegiate competition is an organized contest in which teams or individuals representing different colleges or universities compete against one another under agreed-upon rules.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:21 p.m.