Triple
T12986770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard J. Lamade Stadium |
E321787
|
entity |
| Predicate | hasOutfieldFenceHeight |
P24089
|
FINISHED |
| Object | approximately 8 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 8 feet | Statement: [Howard J. Lamade Stadium, hasOutfieldFenceHeight, approximately 8 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldFenceHeight Context triple: [Howard J. Lamade Stadium, hasOutfieldFenceHeight, approximately 8 feet]
-
A.
outfieldWallHeight
chosen
Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
-
B.
hasOutfieldFeature
Indicates that an entity possesses or includes a specific feature or characteristic located in its outfield area.
-
C.
outfieldWallDistance
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
-
D.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
E.
fieldingAbility
Indicates the level or quality of an entity’s skill and effectiveness in performing fielding actions in a game or sport.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:40 p.m.