Triple
T32015704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Nevada Field |
E817531
|
entity |
| Predicate | distanceToHomePlateToLeftField |
P22064
|
FINISHED |
| Object | approximately 338 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 338 feet | Statement: [Greater Nevada Field, distanceToHomePlateToLeftField, approximately 338 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHomePlateToLeftField Context triple: [Greater Nevada Field, distanceToHomePlateToLeftField, approximately 338 feet]
-
A.
distanceToHomePlate
Indicates the measured distance between an entity’s current position and home plate.
-
B.
pitchingDistance
Indicates the measured distance between the location from which something is pitched or thrown and its intended target or reference point.
-
C.
hasHomeRunDistanceApprox
Indicates that an entity (typically a home run event) is associated with an approximate measured distance the ball traveled.
-
D.
outfieldWallDistance
chosen
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
E.
fieldDistanceBetweenBases
Indicates the measured distance separating two bases within a field or playing area.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a030f1480148190a5e8c8926ded252c |
completed | May 12, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a030e7f5fa481909696733defefcc20 |
completed | May 12, 2026, 11:26 a.m. |
Created at: May 1, 2026, 12:16 a.m.