Triple
T37575054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Griffey Sr. and Ken Griffey Jr. |
E934794
|
entity |
| Predicate | accomplished |
P158464
|
FINISHED |
| Object | hit back-to-back home runs in same MLB game |
—
|
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: hit back-to-back home runs in same MLB game | Statement: [Ken Griffey Sr. and Ken Griffey Jr., accomplished, hit back-to-back home runs in same MLB game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accomplished Context triple: [Ken Griffey Sr. and Ken Griffey Jr., accomplished, hit back-to-back home runs in same MLB game]
-
A.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
B.
coAchieved
chosen
Indicates that two or more entities jointly accomplished or attained the same goal, outcome, or achievement.
-
C.
achievedThrough
Indicates that a result, state, or outcome is brought about or realized by means of a specified method, process, or action.
-
D.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
E.
finished
Indicates that an entity has completed an action, process, or state, reaching its end point.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.