Triple
T10896032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cody Bellinger |
E257311
|
entity |
| Predicate | battedHomeRunsIn2019Season |
P13675
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [Cody Bellinger, battedHomeRunsIn2019Season, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedHomeRunsIn2019Season Context triple: [Cody Bellinger, battedHomeRunsIn2019Season, 47]
-
A.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
-
C.
singleSeasonHomeRuns
chosen
Indicates the number of home runs a player hit during a single baseball season.
-
D.
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.
-
E.
careerHomeRuns
Indicates the total number of home runs an entity has hit over the entire span of their professional career.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.