Triple
T7606165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Walker |
E180108
|
entity |
| Predicate | 1997BattingAverage |
P14861
|
FINISHED |
| Object | .366 |
—
|
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: .366 | Statement: [Larry Walker, 1997BattingAverage, .366]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1997BattingAverage Context triple: [Larry Walker, 1997BattingAverage, .366]
-
A.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
B.
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.
-
C.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
D.
testBattingAverage
Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
-
E.
battingAverageTest
Indicates the statistical relationship between a batter’s number of hits and official at-bats used to evaluate hitting performance.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fe10408190b1c12bb8f911cea8 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.