Triple
T30780998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1931 World Series |
E783810
|
entity |
| Predicate | featuredBallpark |
P587
|
FINISHED |
| Object | Sportsman’s Park |
—
|
NE NERFINISHED |
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: Sportsman’s Park | Statement: [1931 World Series, featuredBallpark, Sportsman’s Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredBallpark Context triple: [1931 World Series, featuredBallpark, Sportsman’s Park]
-
A.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
B.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
C.
ballparkCharacteristic
Indicates a characteristic, feature, or attribute that is associated with a ballpark.
-
D.
hasBallpark
chosen
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
E.
ballparks
Indicates that one entity makes an approximate estimate or rough guess about another entity or quantity.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: April 29, 2026, 8:41 p.m.