Triple
T2959088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaseya Center |
E80001
|
entity |
| Predicate | namingRightsDealAnnouncementDate |
P17374
|
FINISHED |
| Object | 2023-04-04 |
—
|
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: 2023-04-04 | Statement: [Kaseya Center, namingRightsDealAnnouncementDate, 2023-04-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsDealAnnouncementDate Context triple: [Kaseya Center, namingRightsDealAnnouncementDate, 2023-04-04]
-
A.
namingRightsDealAnnounced
chosen
Indicates that an agreement granting naming rights to a property, venue, event, or asset has been formally announced.
-
B.
namingRightsEndYear
Indicates the calendar year in which an entity’s contractual right to have its name associated with another entity (e.g., a venue, event, or asset) expires.
-
C.
acquiredNamingRightsYear
Indicates the year in which an entity obtained the naming rights to another entity (such as a venue, event, or organization).
-
D.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
E.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.