Triple
T11506835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Griffey Sr. |
E272805
|
entity |
| Predicate | battedBackToBackHomeRunsDate |
P99846
|
FINISHED |
| Object | 1990-09-14 |
—
|
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: 1990-09-14 | Statement: [Ken Griffey Sr., battedBackToBackHomeRunsDate, 1990-09-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedBackToBackHomeRunsDate Context triple: [Ken Griffey Sr., battedBackToBackHomeRunsDate, 1990-09-14]
-
A.
gameDateOfFamousHomeRun
Indicates the specific date on which a particular famous home run was hit in a game.
-
B.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
-
C.
opponentBatterInFamousHomeRun
Indicates that the subject was the opposing batter involved in a specific, well-known home run event.
-
D.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
E.
battingMilestone
Indicates reaching a significant achievement or benchmark related to batting performance, such as a notable run total or record.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.