Triple
T32115974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster.com Park |
E820238
|
entity |
| Predicate | namingRightsContext |
P173585
|
FINISHED |
| Object | corporate sponsorship |
—
|
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: corporate sponsorship | Statement: [Monster.com Park, namingRightsContext, corporate sponsorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsContext Context triple: [Monster.com Park, namingRightsContext, corporate sponsorship]
-
A.
namingRightsScope
Indicates the extent or boundaries of what an entity’s naming rights cover within a particular agreement or context.
-
B.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
C.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
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. 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b908810c8190bd58d2d0eee21d40 |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:28 a.m.