Triple
T18571727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Edwards |
E453888
|
entity |
| Predicate | hasBattingStrength |
P54625
|
FINISHED |
| Object | playing sweeps and reverse sweeps |
—
|
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: playing sweeps and reverse sweeps | Statement: [Scott Edwards, hasBattingStrength, playing sweeps and reverse sweeps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattingStrength Context triple: [Scott Edwards, hasBattingStrength, playing sweeps and reverse sweeps]
-
A.
battingStrength
chosen
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
-
B.
battingPowerplayHistory
Indicates the historical record of batting performances specifically during powerplay overs in past matches or innings.
-
C.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
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.
batsAgainst
Indicates that one participant serves as the batter facing another participant as the opposing pitcher in a baseball matchup.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b021ea4819095fe06be88e74133 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.