Triple
T1602287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEN Arena |
E34419
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | M.E.N. Arena |
E34419
|
NE 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: M.E.N. Arena | Statement: [MEN Arena, hasAlternativeName, M.E.N. Arena]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M.E.N. Arena Context triple: [MEN Arena, hasAlternativeName, M.E.N. Arena]
-
A.
MEN Arena
chosen
MEN Arena was the former name of Manchester Arena, a major indoor entertainment and sports venue in Manchester, England.
-
B.
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.
-
C.
MVP Arena
MVP Arena is a multi-purpose indoor sports and entertainment venue located in Albany, New York.
-
D.
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.
-
E.
Artland Arena
Artland Arena is a multi-purpose indoor sports and events venue located in Quakenbrück, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62292d1c819080b597199dc6b8d5 |
completed | March 6, 2026, 5:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51bcdebc81909520786c560598b6 |
completed | March 8, 2026, 10:38 a.m. |
Created at: March 4, 2026, 7:28 p.m.