Triple
T2236721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mickey Cochrane |
E49297
|
entity |
| Predicate | onBasePercentage |
P26689
|
FINISHED |
| Object | .419 |
—
|
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: .419 | Statement: [Mickey Cochrane, onBasePercentage, .419]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onBasePercentage Context triple: [Mickey Cochrane, onBasePercentage, .419]
-
A.
OnBasePercentage
chosen
Indicates the frequency with which a batter successfully reaches base (by hit, walk, or hit-by-pitch) per plate appearance.
-
B.
creditPercentage
Indicates the proportion or share of credit assigned to an entity in relation to a particular outcome, contribution, or transaction.
-
C.
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.
-
D.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
E.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.