Triple
T5165034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma Rainiers |
E116529
|
entity |
| Predicate | homeStadiumOpeningYear |
P13632
|
FINISHED |
| Object | Cheney Stadium 1960 |
—
|
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: Cheney Stadium 1960 | Statement: [Tacoma Rainiers, homeStadiumOpeningYear, Cheney Stadium 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumOpeningYear Context triple: [Tacoma Rainiers, homeStadiumOpeningYear, Cheney Stadium 1960]
-
A.
stadiumOpeningYear
chosen
Indicates the calendar year in which a stadium was officially opened for use.
-
B.
homeStadiumDuringNicknameEra
Indicates the stadium that served as a team’s home field during the specific period when it used a particular nickname.
-
C.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
homeStadiumAppearances
Indicates the number of times an entity has appeared or participated in events held at its designated home stadium.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792936d48190825da8826448c1da |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.