Triple
T14011292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosaic Stadium |
E337083
|
entity |
| Predicate | openedForRoughridersSeason |
P54214
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Mosaic Stadium, openedForRoughridersSeason, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForRoughridersSeason Context triple: [Mosaic Stadium, openedForRoughridersSeason, 2017]
-
A.
openedForFootballSeason
chosen
Indicates that a venue or facility has begun operating or is made available specifically for use during the football season.
-
B.
openingForSeason
Indicates the event or action of beginning a new operational or active season for something (such as a venue, activity, or service).
-
C.
openSeason
Indicates that a period has begun during which a particular activity (such as hunting, fishing, or competition) is officially allowed or actively underway.
-
D.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
E.
openSeasonally
Indicates that an entity operates or is accessible only during specific seasons or times of the year.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed5cfd0819085b9c860b119a9de |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.