Triple
T24103273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee Brewers Walk of Fame |
E597145
|
entity |
| Predicate | locatedAtVenueFormerName |
P83166
|
FINISHED |
| Object | Miller Park |
—
|
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: Miller Park | Statement: [Milwaukee Brewers Walk of Fame, locatedAtVenueFormerName, Miller Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtVenueFormerName Context triple: [Milwaukee Brewers Walk of Fame, locatedAtVenueFormerName, Miller Park]
-
A.
venueFormerName
chosen
Indicates that a venue previously had a different official name than it has currently.
-
B.
formerVenueLocation
Indicates that a location previously served as the venue for an entity or event but no longer does so.
-
C.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
-
D.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
E.
venueFormerNameManaged
Indicates that a venue was previously known by a different name during the period it was managed by a particular entity.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2ad01881909aa5a3c300009086 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11 p.m.