Triple
T30705706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrovsky Stadium |
E781745
|
entity |
| Predicate | replacedByAsHomeStadium |
P61007
|
FINISHED |
| Object | Gazprom Arena |
—
|
NE NERFINISHED |
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: Gazprom Arena | Statement: [Petrovsky Stadium, replacedByAsHomeStadium, Gazprom Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByAsHomeStadium Context triple: [Petrovsky Stadium, replacedByAsHomeStadium, Gazprom Arena]
-
A.
replacedByAsMainFootballVenue
Indicates that one football venue has been superseded by another as the primary location for hosting football events.
-
B.
replacedStadiumForTeam
chosen
Indicates that one stadium succeeded and took over the role of another as the home venue for a particular team.
-
C.
replacedByAsPrimaryNHLVenue
Indicates that one venue has been superseded by another as the primary location for hosting NHL games.
-
D.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
E.
formerHomeTeamReplaced
Indicates that one team previously played its home games at a venue but was later replaced there by another team.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 29, 2026, 8:35 p.m.