Triple
T16704802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adley Rutschman |
E405940
|
entity |
| Predicate | battedPosition |
P57164
|
FINISHED |
| Object | middle of the batting order |
—
|
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: middle of the batting order | Statement: [Adley Rutschman, battedPosition, middle of the batting order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedPosition Context triple: [Adley Rutschman, battedPosition, middle of the batting order]
-
A.
battingPosition
chosen
Indicates the specific order or spot in which a player appears in a batting lineup or batting order.
-
B.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
C.
positionInBaseball
Indicates the specific defensive role or fielding position that a player occupies on a baseball team.
-
D.
battedIn
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
E.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3833496dc8190ae4b4a03ba04d69d |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.