Triple
T14357620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Pérez |
E356011
|
entity |
| Predicate | battedInRuns |
P60115
|
FINISHED |
| Object | high RBI totals |
—
|
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: high RBI totals | Statement: [Tony Pérez, battedInRuns, high RBI totals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedInRuns Context triple: [Tony Pérez, battedInRuns, high RBI totals]
-
A.
battedRuns
Indicates that a player scored a specified number of runs while batting in a cricket (or similar bat-and-ball) context.
-
B.
RunsBattedIn
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
C.
battedIn
chosen
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.
-
D.
battedWalks
Indicates that one entity walked to first base as a result of a plate appearance in which they were batting (i.e., received a base on balls while at bat).
-
E.
battedLeadoff
Indicates that an entity served as the first batter in the lineup for a team in a particular game or context.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:15 a.m.