Triple
T2473547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary SouthShore RailCats |
E55031
|
entity |
| Predicate | homeBallparkCapacity |
P3507
|
FINISHED |
| Object | approximately 6000 |
—
|
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: approximately 6000 | Statement: [Gary SouthShore RailCats, homeBallparkCapacity, approximately 6000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeBallparkCapacity Context triple: [Gary SouthShore RailCats, homeBallparkCapacity, approximately 6000]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
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.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
E.
ballparkCharacteristic
Indicates a characteristic, feature, or attribute that is associated with a ballpark.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.