Triple
T3059850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League |
E60569
|
entity |
| Predicate | formerlyUsedDesignatedHitter |
P44847
|
FINISHED |
| Object | no (before 2022) |
—
|
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: no (before 2022) | Statement: [National League, formerlyUsedDesignatedHitter, no (before 2022)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyUsedDesignatedHitter Context triple: [National League, formerlyUsedDesignatedHitter, no (before 2022)]
-
A.
usesDesignatedHitterRule
Indicates that a baseball league, team, or game employs the designated hitter rule, allowing a player to bat in place of the pitcher.
-
B.
designatedHitterRuleLeagueWideSince
Indicates that the designated hitter rule has been in effect across an entire league starting from a specified time.
-
C.
homeRunDerbyChampion
Indicates that the subject is the winner of a home run derby competition.
-
D.
convertedToPitcher
Indicates that an entity changed roles or status to become a pitcher.
-
E.
roleInBaseballHistory
Indicates the specific part or contribution an entity has within the broader narrative or development of baseball history.
- F. None of above. chosen
Provenance (4 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9cf9188190b43f50edc009030d |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.