Triple
T19804461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinergy Corporation |
E475773
|
entity |
| Predicate | namingRightsVenueType |
P15852
|
FINISHED |
| Object | baseball stadium |
—
|
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: baseball stadium | Statement: [Cinergy Corporation, namingRightsVenueType, baseball stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRightsVenueType Context triple: [Cinergy Corporation, namingRightsVenueType, baseball stadium]
-
A.
namingRightsLocation
chosen
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
B.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
C.
hasSportsVenueType
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
D.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
E.
namingRightsScope
Indicates the extent or boundaries of what an entity’s naming rights cover within a particular agreement or context.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65427546c819082c8eb0d63e3f5fe |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.