Triple
T413084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Mobile Park |
E9532
|
entity |
| Predicate | namingRightsEffectiveFrom |
P6561
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [T-Mobile Park, namingRightsEffectiveFrom, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsEffectiveFrom Context triple: [T-Mobile Park, namingRightsEffectiveFrom, 2019]
-
A.
namingRightsHolder
Indicates which entity holds the official right to name or brand another entity (such as a venue, event, or asset).
-
B.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
C.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
D.
dateGranted
chosen
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
E.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.