Triple
T14013427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granny Hamner |
E337143
|
entity |
| Predicate | battedInWorldSeries |
P112440
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Granny Hamner, battedInWorldSeries, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedInWorldSeries Context triple: [Granny Hamner, battedInWorldSeries, 1950]
-
A.
battedInLeague
Indicates that an entity (typically a player) participated as a batter in a specified baseball league.
-
B.
managedInWorldSeries
Indicates that a person served as a manager for a team participating in a World Series.
-
C.
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.
-
D.
playedInWorldSeriesWith
Indicates that two or more players were teammates in at least one World Series.
-
E.
opponentInWorldSeries
Indicates that two entities were opposing teams facing each other in a World Series matchup.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.