Triple
T25781524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 Cy Young Award season |
E649302
|
entity |
| Predicate | positionOfWinners |
P14863
|
FINISHED |
| Object | pitcher |
—
|
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: pitcher | Statement: [1985 Cy Young Award season, positionOfWinners, pitcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfWinners Context triple: [1985 Cy Young Award season, positionOfWinners, pitcher]
-
A.
positionOfTypicalWinners
Indicates the usual or most common placement or ranking that winners occupy in a given context or competition.
-
B.
positionOfWinner
chosen
Indicates the relationship that identifies which entity holds the winning position or rank in a competition or contest.
-
C.
rarityOfWinnersByPosition
Indicates how uncommon or infrequent winners are for each specific position.
-
D.
recordWinners
Indicates that an entity documents or stores information about the winners of a particular event, contest, or competition.
-
E.
positionOfAwardedPlayer
Indicates the specific playing position or role on a team held by the player who received the award.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 22, 2026, 5:38 a.m.