Triple
T27197578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potomac Nationals |
E683644
|
entity |
| Predicate | playedAtBallparkUntil |
P30600
|
FINISHED |
| Object | Pfitzner Stadium, 2019 |
—
|
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: Pfitzner Stadium, 2019 | Statement: [Potomac Nationals, playedAtBallparkUntil, Pfitzner Stadium, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedAtBallparkUntil Context triple: [Potomac Nationals, playedAtBallparkUntil, Pfitzner Stadium, 2019]
-
A.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
B.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
C.
playedHomeGamesUntil
chosen
Indicates the period up to which a team or player hosted their home games at a particular venue.
-
D.
previousHomeBallparkFor
Indicates that a specified ballpark formerly served as the home venue for a particular sports team or organization.
-
E.
usesBallparksIn
Indicates that one entity makes use of or operates within specific ballparks located in a particular place or context.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 9:35 a.m.