Triple
T31573104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Wildcats baseball |
E805617
|
entity |
| Predicate | homeVenueNameIncludes |
P150009
|
FINISHED |
| Object | Kentucky Proud Park |
—
|
NE NERFINISHED |
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: Kentucky Proud Park | Statement: [Kentucky Wildcats baseball, homeVenueNameIncludes, Kentucky Proud Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueNameIncludes Context triple: [Kentucky Wildcats baseball, homeVenueNameIncludes, Kentucky Proud Park]
-
A.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
B.
homeVenueName
chosen
Indicates the name of the primary venue or location where an entity (such as a team, event, or organization) regularly hosts its home activities.
-
C.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
D.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
E.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:20 p.m.