Triple
T2523889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Knights |
E55588
|
entity |
| Predicate | previousBallparkClosed |
P5404
|
FINISHED |
| Object | Knights Stadium 2013 |
—
|
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: Knights Stadium 2013 | Statement: [Charlotte Knights, previousBallparkClosed, Knights Stadium 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousBallparkClosed Context triple: [Charlotte Knights, previousBallparkClosed, Knights Stadium 2013]
-
A.
formerBallpark
chosen
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
B.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
C.
ballparkFormerName
Indicates that one name was previously used as the official name of a particular ballpark before it was changed.
-
D.
ballparkOpeningYear
Indicates the calendar year in which a ballpark first officially opened for use.
-
E.
mostGamesBallpark
Indicates that the referenced ballpark is the venue where an entity (typically a team or player) has played the greatest number of its games compared to all other ballparks.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.