Triple
T4173961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegiant Stadium |
E86430
|
entity |
| Predicate | openedForFootballSeason |
P54214
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Allegiant Stadium, openedForFootballSeason, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForFootballSeason Context triple: [Allegiant Stadium, openedForFootballSeason, 2020]
-
A.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
B.
openSeason
Indicates that a period has begun during which a particular activity (such as hunting, fishing, or competition) is officially allowed or actively underway.
-
C.
hasOpeningMatchSeason
Indicates that an entity has a specific match designated as the opening match of a particular season.
-
D.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
-
E.
closedSeason
Indicates that a period of time is designated during which a particular activity (such as hunting, fishing, or harvesting) is legally prohibited or restricted.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af07059d288190a1ea79449414fbce |
completed | March 9, 2026, 5:44 p.m. |
Created at: March 9, 2026, 3:45 p.m.