Triple
T9535926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1928 World Series |
E230013
|
entity |
| Predicate | LouGehrigHomeRunsInSeries |
P14862
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [1928 World Series, LouGehrigHomeRunsInSeries, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LouGehrigHomeRunsInSeries Context triple: [1928 World Series, LouGehrigHomeRunsInSeries, 4]
-
A.
ledLeagueInHomeRuns
Indicates that the subject achieved the highest number of home runs in a particular league over a specified season or time period.
-
B.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
C.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
D.
homeRunsNotedFor
Indicates that an entity is recognized or recorded specifically for its home runs.
-
E.
careerHomeRuns
Indicates the total number of home runs an entity has hit over the entire span of their professional career.
- 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.