Triple
T23954844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Hornsby |
E603755
|
entity |
| Predicate | battingTitlesWon |
P17266
|
FINISHED |
| Object | multiple National League batting titles |
—
|
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: multiple National League batting titles | Statement: [Rogers Hornsby, battingTitlesWon, multiple National League batting titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingTitlesWon Context triple: [Rogers Hornsby, battingTitlesWon, multiple National League batting titles]
-
A.
battingTitleWins
chosen
Indicates the number of times a player has won a batting title in a given league or competition.
-
B.
battingTitleYear
Indicates the specific year in which an entity received or held a batting title.
-
C.
baseballAchievement
Indicates that an entity has attained a notable accomplishment, record, or honor specifically within the context of baseball.
-
D.
worldSeriesTitles
Indicates the number of World Series championship titles an entity (typically a baseball team) has won.
-
E.
hasWorldSeriesTitle
Indicates that an entity (typically a baseball team) has won at least one World Series championship title.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d616ec81908c796894f40f3015 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.