Triple
T22379771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 MLB All-Star Game |
E553238
|
entity |
| Predicate | visitingLeagueAbbreviation |
P12209
|
FINISHED |
| Object | NL |
—
|
LITERAL FINISHED |
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: NL | Statement: [1995 MLB All-Star Game, visitingLeagueAbbreviation, NL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingLeagueAbbreviation Context triple: [1995 MLB All-Star Game, visitingLeagueAbbreviation, NL]
-
A.
visitingLeague
chosen
Indicates that a sports league is acting as the visiting or away league in a particular game, event, or matchup.
-
B.
leagueAbbreviation
Indicates that an entity is identified by a shortened or abbreviated form of its league name.
-
C.
awayTeamAbbreviation
Indicates the abbreviated code or short-form identifier used to represent the away team in a game or match.
-
D.
rivalTeamAbbreviation
Indicates that one team is identified as the rival of another team, using the rival team's standard abbreviation.
-
E.
visitingTeamFranchise
Indicates that one franchise is the visiting (away) team in a particular game or matchup involving another franchise.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582afe6c819093940f9d817c64a8 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.