Triple
T19129169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League Park (Cincinnati) |
E468268
|
entity |
| Predicate | homeVenueUntil |
P40950
|
FINISHED |
| Object | Palace of the Fans opening |
—
|
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: Palace of the Fans opening | Statement: [League Park (Cincinnati), homeVenueUntil, Palace of the Fans opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueUntil Context triple: [League Park (Cincinnati), homeVenueUntil, Palace of the Fans opening]
-
A.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
B.
homeVenueDuration
Indicates the length of time an entity uses or has used a particular venue as its home location for events or activities.
-
C.
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.
-
D.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
E.
homeVenueOpened
chosen
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cf8d348190b27fc7d7d39f46f1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.