Triple
T15911025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Wilkinson |
E385846
|
entity |
| Predicate | winningStreakPeriod |
P88862
|
FINISHED |
| Object | 1953–1957 |
—
|
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: 1953–1957 | Statement: [Bud Wilkinson, winningStreakPeriod, 1953–1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningStreakPeriod Context triple: [Bud Wilkinson, winningStreakPeriod, 1953–1957]
-
A.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
B.
endedStreakOf
Indicates that one entity caused another entity's ongoing streak (such as a series of successes, events, or performances) to come to an end.
-
C.
ALWinningStreakExtendedTo
Indicates that an existing winning streak in the American League (AL) has been continued and now reaches a specified new length.
-
D.
notableStreakMatch
Indicates that a match is part of a significant or noteworthy streak (such as consecutive wins, losses, or performances) associated with an entity.
-
E.
streak
chosen
Indicates that an entity is experiencing a continuous run of the same outcome or behavior across multiple consecutive events or time points.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.