Triple
T25927083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory Field |
E653334
|
entity |
| Predicate | predecessorVenueOfTeam |
P65456
|
FINISHED |
| Object | Bush Stadium |
—
|
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: Bush Stadium | Statement: [Victory Field, predecessorVenueOfTeam, Bush Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorVenueOfTeam Context triple: [Victory Field, predecessorVenueOfTeam, Bush Stadium]
-
A.
homeVenueOfPredecessorClubOf
Indicates that a venue served as the home ground for a club that was the predecessor of the referenced club.
-
B.
successorVenueForTeam
chosen
Indicates that one venue has replaced another as the home or primary hosting location for a particular team.
-
C.
predecessorLeagueInCity
Indicates that one sports league previously operated in a given city before another league took its place there.
-
D.
predecessorBallparkTeam2
Indicates that one ballpark team is the immediate predecessor of another ballpark team in a sequence or historical succession.
-
E.
teamPredecessorCity
Indicates that one sports team previously based in a given city is the predecessor or earlier incarnation of another team in that city.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 8:35 a.m.