Triple
T3803174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PK Park |
E91737
|
entity |
| Predicate | distanceToLeftField |
P22064
|
FINISHED |
| Object | 320 ft |
—
|
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: 320 ft | Statement: [PK Park, distanceToLeftField, 320 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLeftField Context triple: [PK Park, distanceToLeftField, 320 ft]
-
A.
outfieldWallDistance
chosen
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
B.
distanceToHomePlate
Indicates the measured distance between an entity’s current position and home plate.
-
C.
distanceToBorder
Indicates the measured or estimated spatial separation between a given entity or location and the nearest relevant border or boundary.
-
D.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
E.
fieldSide
Indicates the relative side or position of something with respect to a defined 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.