Triple
T20926393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 College World Series |
E515354
|
entity |
| Predicate | mostOutstandingPlayerPosition |
P109984
|
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: [2017 College World Series, mostOutstandingPlayerPosition, pitcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostOutstandingPlayerPosition Context triple: [2017 College World Series, mostOutstandingPlayerPosition, pitcher]
-
A.
MVPposition
Indicates the position or role in which an entity served when it was recognized as the Most Valuable Player (MVP).
-
B.
mostOutstandingPlayerTeam
Indicates that a team is the one for which a given player was recognized as the most outstanding (e.g., MVP) during a specific context or period.
-
C.
mostCapsPlayer
Indicates that the subject is the player who has made the highest number of appearances (caps) for a given team or context.
-
D.
positionOfAwardedPlayer
chosen
Indicates the specific playing position or role on a team held by the player who received the award.
-
E.
positionOfNotablePlayer
Indicates the role or playing position that a notable player occupies within a team or sport.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f65200b08190ac208204a20f5a6a |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.