Triple
T1351440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Lowell |
E28890
|
entity |
| Predicate | battedAverageCareerApprox |
P7538
|
FINISHED |
| Object | .279 |
—
|
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: .279 | Statement: [Mike Lowell, battedAverageCareerApprox, .279]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedAverageCareerApprox Context triple: [Mike Lowell, battedAverageCareerApprox, .279]
-
A.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
B.
careerBattingAverage
chosen
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
C.
careerOnBasePercentage
Indicates a player's on-base percentage averaged over the entire duration of their career.
-
D.
onBasePlusSluggingCareer
Indicates a player’s career-long combined performance in getting on base and hitting for power, typically measured as on-base percentage plus slugging percentage.
-
E.
careerSluggingPercentage
Indicates the overall slugging percentage a player has achieved across their entire 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.