Triple
T38079895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGA–GT rivalry |
E950821
|
entity |
| Predicate | gamePlayedOnOrNear |
P191067
|
FINISHED |
| Object | Thanksgiving weekend |
—
|
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: Thanksgiving weekend | Statement: [UGA–GT rivalry, gamePlayedOnOrNear, Thanksgiving weekend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePlayedOnOrNear Context triple: [UGA–GT rivalry, gamePlayedOnOrNear, Thanksgiving weekend]
-
A.
gamePlayedIn
Indicates that a particular game or match took place at or within a specified location or venue.
-
B.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
C.
homeGamesPlayedOn
Indicates that the specified home team plays its home games on the given date, day, or at the specified venue.
-
D.
finalUsuallyPlayedIn
Indicates that an event or competition’s final round is typically held in a particular location or venue.
-
E.
gamesOf
Indicates a relationship where one entity is the set, list, or collection of games associated with another entity.
- F. None of above. chosen
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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.