Triple
T6852184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paycor Stadium |
E158045
|
entity |
| Predicate | namingRightsDealEffectiveSeason |
P15851
|
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: [Paycor Stadium, namingRightsDealEffectiveSeason, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsDealEffectiveSeason Context triple: [Paycor Stadium, namingRightsDealEffectiveSeason, 2022]
-
A.
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.
-
B.
acquiredNamingRightsYear
chosen
Indicates the year in which an entity obtained the naming rights to another entity (such as a venue, event, or organization).
-
C.
namingRightsDealAnnounced
Indicates that an agreement granting naming rights to a property, venue, event, or asset has been formally announced.
-
D.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
E.
namingRightsReplaced
Indicates that one entity’s naming rights to something have been superseded or taken over by another entity’s naming rights.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84e6fb08190915954be5b0df2d8 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.