Triple
T1343533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Yaroslavl |
E28518
|
entity |
| Predicate | homeArena |
P373
|
FINISHED |
| Object |
Arena 2000
Arena 2000 is a modern multi-purpose indoor ice hockey arena in Yaroslavl, Russia, best known as the home venue of the Lokomotiv Yaroslavl hockey club.
|
E154079
|
NE FINISHED |
How this triple was built (4 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: Arena 2000 | Statement: [Lokomotiv Yaroslavl, homeArena, Arena 2000]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arena 2000 Context triple: [Lokomotiv Yaroslavl, homeArena, Arena 2000]
-
A.
ST Arena
ST Arena was the former name of Ondrej Nepela Arena, a major multi-purpose ice hockey and events venue in Bratislava, Slovakia.
-
B.
Arenas
Arenas is a Spanish-origin surname most notably associated with former NBA All-Star basketball player Gilbert Arenas.
-
C.
Arena
Arena is a surname most prominently associated with Bruce Arena, a highly successful American soccer coach and former manager of the United States men's national team.
-
D.
Artland Arena
Artland Arena is a multi-purpose indoor sports and events venue located in Quakenbrück, Germany.
-
E.
T-Com Arena
T-Com Arena was the former sponsored name of Bratislava’s main ice hockey and multi-purpose venue now known as Ondrej Nepela Arena.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Arena 2000 Triple: [Lokomotiv Yaroslavl, homeArena, Arena 2000]
Generated description
Arena 2000 is a modern multi-purpose indoor ice hockey arena in Yaroslavl, Russia, best known as the home venue of the Lokomotiv Yaroslavl hockey club.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Arena 2000 Target entity description: Arena 2000 is a modern multi-purpose indoor ice hockey arena in Yaroslavl, Russia, best known as the home venue of the Lokomotiv Yaroslavl hockey club.
-
A.
ST Arena
ST Arena was the former name of Ondrej Nepela Arena, a major multi-purpose ice hockey and events venue in Bratislava, Slovakia.
-
B.
Arenas
Arenas is a Spanish-origin surname most notably associated with former NBA All-Star basketball player Gilbert Arenas.
-
C.
Arena
Arena is a surname most prominently associated with Bruce Arena, a highly successful American soccer coach and former manager of the United States men's national team.
-
D.
Artland Arena
Artland Arena is a multi-purpose indoor sports and events venue located in Quakenbrück, Germany.
-
E.
T-Com Arena
T-Com Arena was the former sponsored name of Bratislava’s main ice hockey and multi-purpose venue now known as Ondrej Nepela Arena.
- F. None of above. chosen
Provenance (5 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acc632cbc88190a64897f1b101c699 |
completed | March 8, 2026, 12:43 a.m. |
| NEDg | Description generation | batch_69acc6dbd80881908d640ee204ce9a12 |
completed | March 8, 2026, 12:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69acc8199f508190a86c18ad9085d341 |
completed | March 8, 2026, 12:51 a.m. |
Created at: March 1, 2026, 7:56 p.m.