Triple
T4236981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lance Berkman |
E94716
|
entity |
| Predicate | onBasePercentageMLB |
P26689
|
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: [Lance Berkman, onBasePercentageMLB, .406]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onBasePercentageMLB Context triple: [Lance Berkman, onBasePercentageMLB, .406]
-
A.
OnBasePercentage
chosen
Indicates the frequency with which a batter successfully reaches base (by hit, walk, or hit-by-pitch) per plate appearance.
-
B.
onBasePlusSlugging
Indicates a relationship where a player’s offensive performance is quantified by combining their on-base percentage with their slugging percentage into a single metric.
-
C.
careerOnBasePercentage
Indicates a player's on-base percentage averaged over the entire duration of their career.
-
D.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
E.
homeRunRate
Indicates the frequency at which a player or team hits home runs relative to a specified number of opportunities (such as at-bats, plate appearances, or games).
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e7422a88190955f5f4347fa80d2 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.