Triple
T18765486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League home run leader |
E458882
|
entity |
| Predicate | recordMostHomeRunsInSeasonNumber |
P13674
|
FINISHED |
| Object | 73 |
—
|
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: 73 | Statement: [National League home run leader, recordMostHomeRunsInSeasonNumber, 73]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordMostHomeRunsInSeasonNumber Context triple: [National League home run leader, recordMostHomeRunsInSeasonNumber, 73]
-
A.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
B.
singleSeasonHomeRunRecordSet
chosen
Indicates that an entity established a new record for the most home runs hit in a single season.
-
C.
singleSeasonHomeRuns
Indicates the number of home runs a player hit during a single baseball season.
-
D.
homeRunLeaderSeasons
Indicates the seasons in which a given player led a league or competition in home runs.
-
E.
homeRunRecordHolder
Indicates that the subject holds the record for the most home runs, typically within a specified league, season, or career context.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d83ae10819094b3298cb8256327 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.