Triple
T17701030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford Boxes |
E441299
|
entity |
| Predicate | ballparkOrientation |
P25457
|
FINISHED |
| Object | left-field line |
—
|
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: left-field line | Statement: [Crawford Boxes, ballparkOrientation, left-field line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballparkOrientation Context triple: [Crawford Boxes, ballparkOrientation, left-field line]
-
A.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
B.
ballparkCharacteristic
chosen
Indicates a characteristic, feature, or attribute that is associated with a ballpark.
-
C.
ballparkLocatedOn
Indicates that a ballpark is situated on or directly associated with a specific street, road, or thoroughfare.
-
D.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
E.
ballparkAlsoKnownAs
Indicates that a ballpark is referred to by an alternative name or alias.
- 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.