Triple
T31751930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Vegas Aviators |
E810444
|
entity |
| Predicate | previousBallparkLocation |
P39649
|
FINISHED |
| Object | Downtown Las Vegas, Nevada |
—
|
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: Downtown Las Vegas, Nevada | Statement: [Las Vegas Aviators, previousBallparkLocation, Downtown Las Vegas, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousBallparkLocation Context triple: [Las Vegas Aviators, previousBallparkLocation, Downtown Las Vegas, Nevada]
-
A.
formerHomeBallparkLocation
chosen
Indicates the location where an entity’s home ballpark used to be situated before it moved or was replaced.
-
B.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
C.
previousHomeBallparkFor
Indicates that a specified ballpark formerly served as the home venue for a particular sports team or organization.
-
D.
ballparkFormerName
Indicates that one name was previously used as the official name of a particular ballpark before it was changed.
-
E.
homeBallparkSubsequentName
Indicates that a team's home ballpark later became known by a different name.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 30, 2026, 11:28 p.m.