Triple
T38079849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | traditionalGameTiming |
P79963
|
FINISHED |
| Object | end of regular season |
—
|
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: end of regular season | Statement: [Georgia vs. Georgia Tech, traditionalGameTiming, end of regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalGameTiming Context triple: [Georgia vs. Georgia Tech, traditionalGameTiming, end of regular season]
-
A.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
-
B.
typicalGameTime
Indicates the usual or expected amount of time a game takes to play.
-
C.
inGameTimePeriod
Indicates that an event, state, or action occurs within a specified time period in the context of a game.
-
D.
timeDuringMatch
Indicates that a specified time or time interval occurs within the duration of a particular match or game.
-
E.
competitionTiming
chosen
Indicates the temporal relationship or scheduling of when a competition or competitive event takes place.
- 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_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:21 p.m.