Triple
T635011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Stadium |
E16603
|
entity |
| Predicate | namingRightsDealAnnounced |
P17374
|
FINISHED |
| Object | 2013-07-25 |
—
|
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: 2013-07-25 | Statement: [AT&T Stadium, namingRightsDealAnnounced, 2013-07-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsDealAnnounced Context triple: [AT&T Stadium, namingRightsDealAnnounced, 2013-07-25]
-
A.
acquiredNamingRightsYear
Indicates the year in which an entity obtained the naming rights to another entity (such as a venue, event, or organization).
-
B.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
C.
namingRightsHolder
Indicates which entity holds the official right to name or brand another entity (such as a venue, event, or asset).
-
D.
renamedAsCapitalOneArena
Indicates that an entity has undergone a name change to become "Capital One Arena."
-
E.
sportsRights
Indicates that one entity holds legal rights or permissions related to broadcasting, distributing, or otherwise commercially exploiting a sports event or sports content in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.