Triple
T38079860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | featuresTeamColorsTeam2 |
P4834
|
FINISHED |
| Object | old gold and white |
—
|
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: old gold and white | Statement: [Georgia vs. Georgia Tech, featuresTeamColorsTeam2, old gold and white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTeamColorsTeam2 Context triple: [Georgia vs. Georgia Tech, featuresTeamColorsTeam2, old gold and white]
-
A.
formerTeamColors
Indicates that the specified colors were previously used as the official colors of a team in the past, but are no longer current.
-
B.
teamColor
chosen
Indicates the association between a team and the color that represents or identifies it.
-
C.
teamColorsImplied
Indicates that the colors associated with a team are inferred or derived from context rather than explicitly specified.
-
D.
teamColorContext
Indicates the contextual or situational association between a team and its designated color.
-
E.
featuresTeams
Indicates that something prominently presents or includes specific teams as a central element or focus.
- 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.