Triple
T4037517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buck Weaver |
E83860
|
entity |
| Predicate | battingAverage1919WorldSeries |
P14861
|
FINISHED |
| Object | .324 |
—
|
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: .324 | Statement: [Buck Weaver, battingAverage1919WorldSeries, .324]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingAverage1919WorldSeries Context triple: [Buck Weaver, battingAverage1919WorldSeries, .324]
-
A.
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.
-
B.
firstMLBGameResult
Indicates the outcome of an entity’s first game played in Major League Baseball, such as whether it was a win, loss, or other recorded result.
-
C.
battingAverageAgainst
Indicates the average batting performance (e.g., hits per at-bat) that a batter achieves specifically against a particular pitcher, team, or category of opponents.
-
D.
WorldSeriesChampionYears
Indicates the years in which a given team (or entity) won the World Series championship.
-
E.
noHitterYear
Indicates the specific year in which a no-hitter event occurred or was recorded.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb3656f08190aa5286d951013646 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.