Triple
T3730332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Williams |
E79044
|
entity |
| Predicate | 1941battingAverage |
P14861
|
FINISHED |
| Object | .406 |
—
|
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: .406 | Statement: [Ted Williams, 1941battingAverage, .406]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1941battingAverage Context triple: [Ted Williams, 1941battingAverage, .406]
-
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.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
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.
ledLeagueInBattingAverage
Indicates that an entity achieved the highest batting average in a particular league over a specified season or time period.
-
E.
measurementUnitForBattingAverage
Indicates the unit of measurement used to express a batting average in a given context.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb1bb5408190990ea4dfbdab5c68 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.