Triple
T31555333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River City Stadium Management |
E805111
|
entity |
| Predicate | managesTypeOfVenue |
P57781
|
FINISHED |
| Object | minor league 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: minor league baseball stadium | Statement: [River City Stadium Management, managesTypeOfVenue, minor league baseball stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesTypeOfVenue Context triple: [River City Stadium Management, managesTypeOfVenue, minor league baseball stadium]
-
A.
venueManaged
chosen
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a particular venue.
-
B.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
D.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
E.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 30, 2026, 10:12 p.m.