Triple
T38080103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Auburn football rivalry |
E950827
|
entity |
| Predicate | relatedRivalryAuburn |
P156553
|
FINISHED |
| Object | Iron Bowl |
E104787
|
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: Iron Bowl | Statement: [Georgia vs. Auburn football rivalry, relatedRivalryAuburn, Iron Bowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRivalryAuburn Context triple: [Georgia vs. Auburn football rivalry, relatedRivalryAuburn, Iron Bowl]
-
A.
SECChampionshipSeasonsAtAuburn
Indicates the seasons in which Auburn won the Southeastern Conference (SEC) football championship.
-
B.
AuburnHeadCoachingRecord
Indicates the record of an individual's tenure as head coach for Auburn, typically summarizing wins, losses, and related performance statistics.
-
C.
homeStadiumAuburn
Indicates that the referenced stadium serves as the home venue for the Auburn team or organization.
-
D.
nicknameOfRivalryBetween
chosen
Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
-
E.
hasNationalRivalry
Indicates that there is a notable, often historically rooted competitive or adversarial relationship between two nations.
- 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_6a415d4a1820819099b04a1a6c03c34a |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.