Triple
T31751979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma RedHawks |
E810445
|
entity |
| Predicate | homeOpenerBallparkName |
P89345
|
FINISHED |
| Object | Chickasaw Bricktown Ballpark |
—
|
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: Chickasaw Bricktown Ballpark | Statement: [Oklahoma RedHawks, homeOpenerBallparkName, Chickasaw Bricktown Ballpark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeOpenerBallparkName Context triple: [Oklahoma RedHawks, homeOpenerBallparkName, Chickasaw Bricktown Ballpark]
-
A.
ALHomeBallpark
Indicates that a Major League Baseball team’s designated home ballpark is located in the American League.
-
B.
homeBallparkNameFor
chosen
Indicates that one entity is the name of the home ballpark associated with a given team or organization.
-
C.
previousHomeBallparkFor
Indicates that a specified ballpark formerly served as the home venue for a particular sports team or organization.
-
D.
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.
-
E.
homeBallparkCity
Indicates that a sports team’s designated home ballpark is located in a particular city.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab5390208190a05fda888425b9d4 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:28 p.m.