Triple
T30781030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babe Ruth’s alleged called shot in Game 3 |
E783811
|
entity |
| Predicate | hasHomeRunType |
P46257
|
FINISHED |
| Object | solo 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: solo home run | Statement: [Babe Ruth’s alleged called shot in Game 3, hasHomeRunType, solo home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeRunType Context triple: [Babe Ruth’s alleged called shot in Game 3, hasHomeRunType, solo home run]
-
A.
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).
-
B.
hasHomeRunDirection
Indicates the direction in which a home run is hit relative to the playing field or stadium.
-
C.
hasHomeRunDistanceApprox
Indicates that an entity (typically a home run event) is associated with an approximate measured distance the ball traveled.
-
D.
clinchingHomeRunType
Indicates the specific type or category of a home run that clinches or decisively secures a game, series, or title.
-
E.
homeRunAllowedTo
Indicates that one entity (typically a pitcher or team) has allowed a home run to another entity (typically a batter or opposing team).
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 8:41 p.m.