Triple
T25515261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibrant Arena at The MARK |
E639487
|
entity |
| Predicate | namingRightsChange |
P82079
|
FINISHED |
| Object | 2022 |
—
|
LITERAL 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: 2022 | Statement: [Vibrant Arena at The MARK, namingRightsChange, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsChange Context triple: [Vibrant Arena at The MARK, namingRightsChange, 2022]
-
A.
namingRightsReplaced
Indicates that one entity’s naming rights to something have been superseded or taken over by another entity’s naming rights.
-
B.
namingRightsChangeYear
chosen
Indicates the year in which the naming rights for something (such as a venue, event, or asset) were changed from one name or sponsor to another.
-
C.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
D.
namingRightsCity
Indicates that a city holds the naming rights associated with a particular entity, venue, or event.
-
E.
namingRightsHolder
Indicates which entity holds the official right to name or brand another entity (such as a venue, event, or asset).
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8315ef8819094e5a996997bf0d2 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:55 p.m.