Triple
T19976208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida–Tennessee football rivalry |
E493695
|
entity |
| Predicate | TennesseePrimaryColors |
P138131
|
FINISHED |
| Object | orange 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: orange and white | Statement: [Florida–Tennessee football rivalry, TennesseePrimaryColors, orange and white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TennesseePrimaryColors Context triple: [Florida–Tennessee football rivalry, TennesseePrimaryColors, orange and white]
-
A.
coalitionColor
Indicates the color associated with a particular coalition or alliance.
-
B.
countyColours
Indicates that a specific color or set of colors is associated with, represents, or is used to depict a particular county.
-
C.
partyColor
Indicates the political party affiliation or ideological group with which an entity is associated, typically represented by a specific color.
-
D.
nationalColorsRepresented
Indicates that the national colors of an entity are visibly included or symbolically expressed in another entity or context.
-
E.
MemphisRegion
Indicates that something is located in, associated with, or pertains to the Memphis geographic region.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d0f4fb48190ad63afeff3513523 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:26 p.m.