Triple
T25340865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vodafone Arena |
E635407
|
entity |
| Predicate | formerCommercialNameOf |
P65
|
FINISHED |
| Object | John Cain 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: John Cain Arena | Statement: [Vodafone Arena, formerCommercialNameOf, John Cain Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCommercialNameOf Context triple: [Vodafone Arena, formerCommercialNameOf, John Cain Arena]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
C.
promotionFormerName
Indicates that an entity previously operated or was known under a different promotion name before adopting its current one.
-
D.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
E.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 1:32 p.m.