Triple
T14756432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvy |
E346739
|
entity |
| Predicate | hasBattingProfile |
P96341
|
FINISHED |
| Object | right-handed power hitter |
—
|
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: right-handed power hitter | Statement: [Salvy, hasBattingProfile, right-handed power hitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattingProfile Context triple: [Salvy, hasBattingProfile, right-handed power hitter]
-
A.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
-
B.
battingType
chosen
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
C.
battingPowerplayHistory
Indicates the historical record of batting performances specifically during powerplay overs in past matches or innings.
-
D.
associatedWithBattingStyleOfPerson
Indicates a relationship where something is connected to or characterized by the batting style of a specific person.
-
E.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.