Triple
T15262949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jermaine Dye |
E364830
|
entity |
| Predicate | battedAverageIn2006Season |
P14861
|
FINISHED |
| Object | .315 |
—
|
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: .315 | Statement: [Jermaine Dye, battedAverageIn2006Season, .315]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedAverageIn2006Season Context triple: [Jermaine Dye, battedAverageIn2006Season, .315]
-
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.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
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.
battingAverageCategory
Indicates the classification of an entity’s batting average into a defined performance category (e.g., low, medium, high).
-
E.
battingAverageType
Indicates the type or category of a batting average associated with a player or performance (e.g., season, career, situational).
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.