Triple
T31751859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Vegas Ballpark |
E810442
|
entity |
| Predicate | formerTenantName |
P65
|
FINISHED |
| Object | Las Vegas 51s |
—
|
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: Las Vegas 51s | Statement: [Las Vegas Ballpark, formerTenantName, Las Vegas 51s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTenantName Context triple: [Las Vegas Ballpark, formerTenantName, Las Vegas 51s]
-
A.
tenantFormerName
Indicates that the specified name was previously used by the tenant before their current official name.
-
B.
formerOccupant
Indicates that an entity previously occupied a position, role, or place but no longer does so.
-
C.
nicknameOfTenant
Indicates that one entity is the nickname used to refer to a particular tenant.
-
D.
previousAnchorTenant
Indicates that an entity served as the anchor (primary or major) tenant of a property or location at an earlier time, prior to the current anchor tenant.
-
E.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
- 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_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: April 30, 2026, 11:28 p.m.