Triple
T33278688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riders |
E851976
|
entity |
| Predicate | historicalTeamNickname |
P3202
|
FINISHED |
| Object | Ottawa Rough Riders |
—
|
NE NERFINISHED |
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: Ottawa Rough Riders | Statement: [Riders, historicalTeamNickname, Ottawa Rough Riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTeamNickname Context triple: [Riders, historicalTeamNickname, Ottawa Rough Riders]
-
A.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
B.
teamNicknamedAfter
Indicates that a team is commonly referred to by a nickname derived from or inspired by another entity.
-
C.
teamNickname
Indicates the commonly used informal or symbolic name by which a team is known.
-
D.
team1LaterKnownAs
chosen
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
E.
teamColorNicknameOrigin
Indicates the origin or reason behind a sports team’s color and nickname combination.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 1, 2026, 1:32 a.m.