Triple
T29403603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Wayne Wizards |
E745721
|
entity |
| Predicate | movedToBallpark |
P13619
|
FINISHED |
| Object | Parkview Field (as Fort Wayne TinCaps) |
—
|
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: Parkview Field (as Fort Wayne TinCaps) | Statement: [Fort Wayne Wizards, movedToBallpark, Parkview Field (as Fort Wayne TinCaps)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToBallpark Context triple: [Fort Wayne Wizards, movedToBallpark, Parkview Field (as Fort Wayne TinCaps)]
-
A.
movedToCurrentBallpark
chosen
Indicates that an entity (typically a sports team) relocated its home games to its current ballpark or stadium.
-
B.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
C.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
D.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
E.
usesBallparkFor
Indicates that one entity makes use of a particular ballpark facility for its activities or events.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3143948190aeff396f02748fb8 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:52 p.m.