Triple
T6253371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984-06-23 "The Sandberg Game" vs St. Louis Cardinals |
E140099
|
entity |
| Predicate | WillieMcGee_homeRuns |
P14862
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1984-06-23 "The Sandberg Game" vs St. Louis Cardinals, WillieMcGee_homeRuns, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WillieMcGee_homeRuns Context triple: [1984-06-23 "The Sandberg Game" vs St. Louis Cardinals, WillieMcGee_homeRuns, 2]
-
A.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
singleSeasonHomeRuns
Indicates the number of home runs a player hit during a single baseball season.
-
C.
ledLeagueInHomeRuns
Indicates that the subject achieved the highest number of home runs in a particular league over a specified season or time period.
-
D.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
E.
homeRunsNotedFor
Indicates that an entity is recognized or recorded specifically for its home runs.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.