Triple
T593860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1907 World Series |
E17334
|
entity |
| Predicate | designatedHitterUsed |
P3183
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [1907 World Series, designatedHitterUsed, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedHitterUsed Context triple: [1907 World Series, designatedHitterUsed, false]
-
A.
usesDesignatedHitterRule
chosen
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.
decisiveGameBatter
Indicates that a batter participated in a game situation that was decisive in determining the final outcome of the contest.
-
D.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
E.
hasBullpens
Indicates that one entity possesses or includes one or more bullpens associated with it.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd15c5881909b59ed4c88687e7b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.