Triple
T5643111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Stars |
E124315
|
entity |
| Predicate | homeBallparkFeature |
P25457
|
FINISHED |
| Object | short right-field fence |
—
|
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: short right-field fence | Statement: [St. Louis Stars, homeBallparkFeature, short right-field fence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeBallparkFeature Context triple: [St. Louis Stars, homeBallparkFeature, short right-field fence]
-
A.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
B.
homeBallparkOfChampion
Indicates that a particular ballpark serves as the home stadium for a championship-winning team or champion.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
ballparkCharacteristic
chosen
Indicates a characteristic, feature, or attribute that is associated with a ballpark.
-
E.
managedHomeBallpark
Indicates that one entity served as the manager of a sports team while that team was based at or associated with a particular home ballpark.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.