Triple
T30781029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babe Ruth’s alleged called shot in Game 3 |
E783811
|
entity |
| Predicate | hasHomeRunDistanceApprox |
P190059
|
FINISHED |
| Object | 440 feet |
—
|
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: 440 feet | Statement: [Babe Ruth’s alleged called shot in Game 3, hasHomeRunDistanceApprox, 440 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeRunDistanceApprox Context triple: [Babe Ruth’s alleged called shot in Game 3, hasHomeRunDistanceApprox, 440 feet]
-
A.
battedHomeRunDistanceRecord
Indicates that a player hit a home run that set or matched a record for distance.
-
B.
hasHomeRunDirection
Indicates the direction in which a home run is hit relative to the playing field or stadium.
-
C.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
D.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
E.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
- F. None of above. chosen
Provenance (4 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_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 29, 2026, 8:41 p.m.