Triple
T31426027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwyer Stadium |
E801663
|
entity |
| Predicate | originalStadiumOpened |
P13632
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [Dwyer Stadium, originalStadiumOpened, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalStadiumOpened Context triple: [Dwyer Stadium, originalStadiumOpened, 1939]
-
A.
stadiumOpeningYear
chosen
Indicates the calendar year in which a stadium was officially opened for use.
-
B.
stadiumOpeningForGames
Indicates that a stadium is being opened or made available specifically for hosting games or sporting events.
-
C.
openedWithStadium
Indicates that something (such as an event, season, or facility) began or was inaugurated concurrently with the opening of a particular stadium.
-
D.
homeStadiumUsedSince
Indicates that a particular stadium has served as the home venue for a team or organization starting from a specified point in time.
-
E.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: April 30, 2026, 8:53 p.m.