Triple
T3332958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Gordon |
E70074
|
entity |
| Predicate | battedRunsBattedIn |
P26688
|
FINISHED |
| Object | 740+ |
—
|
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: 740+ | Statement: [Alex Gordon, battedRunsBattedIn, 740+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedRunsBattedIn Context triple: [Alex Gordon, battedRunsBattedIn, 740+]
-
A.
RunsBattedIn
chosen
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
B.
clinchingHomeRunRunsBattedIn
Indicates that a particular home run both clinches a game or series and accounts for specific runs batted in (RBIs) scored by the batter.
-
C.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
D.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
-
E.
onBasePlusSlugging
Indicates a relationship where a player’s offensive performance is quantified by combining their on-base percentage with their slugging percentage into a single metric.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb194960081909333c855f06d8b03 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.