Triple
T15816600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saskatoon Rush |
E383494
|
entity |
| Predicate | firstSeasonInSaskatoon |
P120178
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Saskatoon Rush, firstSeasonInSaskatoon, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonInSaskatoon Context triple: [Saskatoon Rush, firstSeasonInSaskatoon, 2016]
-
A.
firstSeasonCity
Indicates that a city is the location where a sports team played its first season.
-
B.
firstSeasonRecorded
Indicates the specific season in which an entity (such as a team, player, or show) was first officially recorded or documented as active.
-
C.
firstSeasonDetermined
Indicates that the initial season associated with an entity has been identified or established.
-
D.
firstSeasonInSanAntonio
Indicates the season in which an entity (such as a team or player) is in San Antonio for the first time.
-
E.
firstSeasonScheduled
Indicates that the initial season of an entity (such as a show, competition, or event series) has been planned and assigned a schedule.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:49 a.m.