Triple
T6515372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Hornsby |
E148242
|
entity |
| Predicate | notableSeasonBattingAverage |
P14861
|
FINISHED |
| Object | .424 |
—
|
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: .424 | Statement: [Rogers Hornsby, notableSeasonBattingAverage, .424]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeasonBattingAverage Context triple: [Rogers Hornsby, notableSeasonBattingAverage, .424]
-
A.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
B.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
C.
battingAverage
chosen
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
D.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
E.
ledLeagueInBattingAverage
Indicates that an entity achieved the highest batting average in a particular league over a specified season or time period.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0d395081908fe6b1f9a912f095 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.