Triple
T15263104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Podsednik |
E364833
|
entity |
| Predicate | hitTypeInNotableGame |
P9490
|
FINISHED |
| Object | walk-off home run |
—
|
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: walk-off home run | Statement: [Scott Podsednik, hitTypeInNotableGame, walk-off home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hitTypeInNotableGame Context triple: [Scott Podsednik, hitTypeInNotableGame, walk-off home run]
-
A.
teamInNotableGame
Indicates that a team participated as one of the competitors in a game or match considered notable or significant.
-
B.
notableGameEvent
Indicates that a specific game is associated with a significant or noteworthy event in its history or context.
-
C.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
D.
notablePlay
chosen
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
E.
game1NotableEvent
Indicates that a specific event is recognized as a notable or significant occurrence within the context of game1.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.