Triple
T31572665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hack Wilson |
E805605
|
entity |
| Predicate | singleSeasonHomeRunLeader |
P121074
|
FINISHED |
| Object | National League 1930 |
—
|
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: National League 1930 | Statement: [Hack Wilson, singleSeasonHomeRunLeader, National League 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleSeasonHomeRunLeader Context triple: [Hack Wilson, singleSeasonHomeRunLeader, National League 1930]
-
A.
singleSeasonHomeRuns
Indicates the number of home runs a player hit during a single baseball season.
-
B.
singleSeasonHomeRunRecordSet
Indicates that an entity established a new record for the most home runs hit in a single season.
-
C.
homeRunLeaderSeasons
Indicates the seasons in which a given player led a league or competition in home runs.
-
D.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
E.
homeRunLeaders
chosen
Indicates the relationship where certain players are identified as having the highest number of home runs, typically within a given league, season, or time span.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:20 p.m.