Triple
T23571047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sandberg Game |
E580111
|
entity |
| Predicate | Ryne SandbergHomeRunType |
P46257
|
FINISHED |
| Object | game-tying home run |
—
|
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: game-tying home run | Statement: [The Sandberg Game, Ryne SandbergHomeRunType, game-tying home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Ryne SandbergHomeRunType Context triple: [The Sandberg Game, Ryne SandbergHomeRunType, game-tying home run]
-
A.
RyneSandberg_RBI
Indicates that Ryne Sandberg recorded a run batted in (RBI) in a game or play.
-
B.
RyneSandberg_totalBases
Indicates the total number of bases Ryne Sandberg accumulated from hits (singles, doubles, triples, and home runs) in his playing career or a specified period.
-
C.
RyneSandberg_team
Indicates the professional baseball team that Ryne Sandberg played for or was a member of.
-
D.
homeRunType
chosen
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
E.
RyneSandberg_awardSeason
Indicates that a specific award season is associated with Ryne Sandberg, during which he received or was considered for an award.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd34c088190bf4f736f1066c920 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:36 p.m.