Triple
T22687336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia–Cornell football rivalry |
E560950
|
entity |
| Predicate | teamColorCornell |
P4834
|
FINISHED |
| Object | Carnelian red |
—
|
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: Carnelian red | Statement: [Columbia–Cornell football rivalry, teamColorCornell, Carnelian red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamColorCornell Context triple: [Columbia–Cornell football rivalry, teamColorCornell, Carnelian red]
-
A.
collegeTeamColor
Indicates that a particular color is one of the official colors associated with a given college sports team.
-
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.
homeTeamColors
Indicates the colors associated with the home team in a sporting event or competition.
-
E.
teamColorContext
Indicates the contextual or situational association between a team and its designated color.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178649aac8190a9d41f5d82895bdf |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.