Triple
T9535924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1928 World Series |
E230013
|
entity |
| Predicate | BabeRuthHomeRunsInSeries |
P14862
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1928 World Series, BabeRuthHomeRunsInSeries, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BabeRuthHomeRunsInSeries Context triple: [1928 World Series, BabeRuthHomeRunsInSeries, 3]
-
A.
babeRuthScorelessInningsStreakRecordType
Indicates that the subject holds or is associated with the record type for Babe Ruth’s streak of consecutive scoreless innings.
-
B.
BabeRuthScorelessInningsStreakExtendedTo
Indicates that Babe Ruth’s streak of consecutive innings without allowing a run was extended to a specified number of innings or up to a specified game or date.
-
C.
babeRuthScorelessInningsStreakEndedInGame
Indicates that Babe Ruth’s streak of consecutive scoreless innings came to an end during the specified game.
-
D.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
E.
babeRuthWalks
Indicates that Babe Ruth is performing the action of walking.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cd6a5c8190835c0910ec38ede3 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.