Triple
T11033852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shot Heard Round the World (baseball) |
E260825
|
entity |
| Predicate | ballsAndStrikes |
P97414
|
FINISHED |
| Object | 1–0 count |
—
|
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: 1–0 count | Statement: [Shot Heard Round the World (baseball), ballsAndStrikes, 1–0 count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballsAndStrikes Context triple: [Shot Heard Round the World (baseball), ballsAndStrikes, 1–0 count]
-
A.
strikeoutsMLB
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
B.
battedRuns
Indicates that a player scored a specified number of runs while batting in a cricket (or similar bat-and-ball) context.
-
C.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
-
D.
battedIn
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
E.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e709648190adbb05197e15ff76 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.