Triple
T34443306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Stampeders–Edmonton Elks rivalry |
E884152
|
entity |
| Predicate | hasTeamColourContrast |
P107982
|
FINISHED |
| Object | red vs green |
—
|
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: red vs green | Statement: [Calgary Stampeders–Edmonton Elks rivalry, hasTeamColourContrast, red vs green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamColourContrast Context triple: [Calgary Stampeders–Edmonton Elks rivalry, hasTeamColourContrast, red vs green]
-
A.
hasTeamColorContrast
chosen
Indicates that there is a sufficient visual contrast between the colors associated with a team and another relevant color set (such as opponents, background, or interface elements).
-
B.
teamColorContext
Indicates the contextual or situational association between a team and its designated color.
-
C.
teamColor
Indicates the association between a team and the color that represents or identifies it.
-
D.
hasClubColor
Indicates that a club or team is associated with a specific color or set of colors used to represent it.
-
E.
introducedTeamColor
Indicates that an entity is responsible for introducing or establishing a particular team color for a team or group.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 2 a.m.