Triple
T19202481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John McGraw |
E480140
|
entity |
| Predicate | onBasePercentageAsPlayer |
P26689
|
FINISHED |
| Object | .466 |
—
|
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: .466 | Statement: [John McGraw, onBasePercentageAsPlayer, .466]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onBasePercentageAsPlayer Context triple: [John McGraw, onBasePercentageAsPlayer, .466]
-
A.
OnBasePercentage
chosen
Indicates the frequency with which a batter successfully reaches base (by hit, walk, or hit-by-pitch) per plate appearance.
-
B.
goalPercentage
Indicates the proportion of a goal that has been achieved relative to its total target.
-
C.
percentageMainOpponent
Indicates the proportion, expressed as a percentage, that a main opponent represents relative to a defined total or context.
-
D.
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.
-
E.
allTimeWinningPercentage
Indicates the proportion of contests or games an entity has won over its entire recorded history, typically expressed as a percentage.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9991ba48190ab92805daec3877b |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:12 p.m.