Triple
T17701023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford Boxes |
E441299
|
entity |
| Predicate | distanceFromHomePlate |
P2610
|
FINISHED |
| Object | approximately 315 feet |
—
|
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: approximately 315 feet | Statement: [Crawford Boxes, distanceFromHomePlate, approximately 315 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromHomePlate Context triple: [Crawford Boxes, distanceFromHomePlate, approximately 315 feet]
-
A.
distanceToHomePlate
chosen
Indicates the measured distance between an entity’s current position and home plate.
-
B.
standardPitchingDistanceSlowpitch
Indicates the regulation distance between the pitcher’s mound and home plate specifically for slowpitch play.
-
C.
distanceToCenterField
Indicates the measured distance from a given point or object to the center of a designated field or playing area.
-
D.
outfieldWallDistance
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
E.
positionInBaseball
Indicates the specific defensive role or fielding position that a player occupies on a baseball team.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:04 a.m.