Triple
T5364087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Warner |
E103087
|
entity |
| Predicate | battingAggression |
P63043
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [David Warner, battingAggression, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingAggression Context triple: [David Warner, battingAggression, high]
-
A.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
-
B.
battedIn
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
C.
battingAverageAgainst
Indicates the average batting performance (e.g., hits per at-bat) that a batter achieves specifically against a particular pitcher, team, or category of opponents.
-
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.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
- F. None of above. chosen
Provenance (4 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865d42508190a1a96121674c1020 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85731dcc8190b4c1fe155967ab81 |
completed | March 20, 2026, 5:35 p.m. |
Created at: March 20, 2026, 2:02 p.m.