Triple
T22778414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metalist Stadium |
E563766
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object |
Traktor Stadium
Traktor Stadium was the original name of Metalist Stadium, a major football venue in Kharkiv, Ukraine.
|
E1556436
|
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: Traktor Stadium | Statement: [Metalist Stadium, formerName, Traktor Stadium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Traktor Stadium Context triple: [Metalist Stadium, formerName, Traktor Stadium]
-
A.
Stadion Ludowy
Stadion Ludowy is a multi-purpose football stadium in Sosnowiec, Poland, primarily known as the home ground of local club Zagłębie Sosnowiec.
-
B.
Stadion Florian Krygier
Stadion Florian Krygier is a football stadium in Szczecin, Poland, primarily known as the long-time home ground of the Polish club Pogoń Szczecin.
-
C.
Polish Army Stadium
Polish Army Stadium is a football stadium in Warsaw, Poland, best known as the home ground of the club Legia Warsaw.
-
D.
Yuvileiny Stadium
Yuvileiny Stadium is a multi-purpose sports arena located in Sumy, Ukraine, primarily used for football matches and athletic events.
-
E.
Monolit stadium
Monolit stadium is a sports venue, likely used for football and other athletic events, that is served by the Stadion Monolit station.
- 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: Traktor Stadium Triple: [Metalist Stadium, formerName, Traktor Stadium]
Generated description
Traktor Stadium was the original name of Metalist Stadium, a major football venue in Kharkiv, Ukraine.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Traktor Stadium Target entity description: Traktor Stadium was the original name of Metalist Stadium, a major football venue in Kharkiv, Ukraine.
-
A.
Stadion Ludowy
Stadion Ludowy is a multi-purpose football stadium in Sosnowiec, Poland, primarily known as the home ground of local club Zagłębie Sosnowiec.
-
B.
Stadion Florian Krygier
Stadion Florian Krygier is a football stadium in Szczecin, Poland, primarily known as the long-time home ground of the Polish club Pogoń Szczecin.
-
C.
Polish Army Stadium
Polish Army Stadium is a football stadium in Warsaw, Poland, best known as the home ground of the club Legia Warsaw.
-
D.
Yuvileiny Stadium
Yuvileiny Stadium is a multi-purpose sports arena located in Sumy, Ukraine, primarily used for football matches and athletic events.
-
E.
Monolit stadium
Monolit stadium is a sports venue, likely used for football and other athletic events, that is served by the Stadion Monolit station.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b631c6881908a6687920923dcf4 |
completed | April 29, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ba79ec6d8819094daf81e5ca9a8d2 |
completed | May 18, 2026, 11:58 p.m. |
| NEDg | Description generation | batch_6a0ba8f30edc8190ac35b422288a3e9f |
completed | May 19, 2026, 12:04 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ba94752c48190a8892cac5ef862b2 |
completed | May 19, 2026, 12:05 a.m. |
Created at: April 17, 2026, 3:28 p.m.