Triple
T25542949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Downing |
E640218
|
entity |
| Predicate | homeRunAllowedTo |
P159137
|
FINISHED |
| Object | Hank Aaron |
—
|
NE NERFINISHED |
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: Hank Aaron | Statement: [Al Downing, homeRunAllowedTo, Hank Aaron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRunAllowedTo Context triple: [Al Downing, homeRunAllowedTo, Hank Aaron]
-
A.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
B.
homeRunInteraction
Indicates an interaction where a batter successfully hits a home run, establishing the event and its participants.
-
C.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
D.
homeRunDefinition
Indicates that an event or action qualifies as a home run according to the rules or criteria of the relevant sport or context.
-
E.
homeRunRate
Indicates the frequency at which a player or team hits home runs relative to a specified number of opportunities (such as at-bats, plate appearances, or games).
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895e458819081cf031b70d20e56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 3:27 p.m.