Triple
T22335897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USC–Stanford football rivalry |
E552145
|
entity |
| Predicate | associatedColorStanford |
P65875
|
FINISHED |
| Object | cardinal 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: cardinal and white | Statement: [USC–Stanford football rivalry, associatedColorStanford, cardinal and white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedColorStanford Context triple: [USC–Stanford football rivalry, associatedColorStanford, cardinal and white]
-
A.
collegeTeamColor
Indicates that a particular color is one of the official colors associated with a given college sports team.
-
B.
officialColor
Indicates the color that is formally designated or recognized as the official one for an entity.
-
C.
colorAssociatedInstitution
Indicates that a particular color is characteristically linked or symbolically connected to an institution.
-
D.
associatedColour
chosen
Indicates that one entity is linked to another as its characteristic or representative colour.
-
E.
colorWhenHeldByUSC
Indicates the color an entity appears or is designated as when it is held, possessed, or controlled by USC.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577f2f208190ac6270ac4581fa15 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.