Triple
T3732173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pensacola Blue Wahoos |
E79089
|
entity |
| Predicate | usesBallparkFor |
P51332
|
FINISHED |
| Object | home games |
—
|
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: home games | Statement: [Pensacola Blue Wahoos, usesBallparkFor, home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBallparkFor Context triple: [Pensacola Blue Wahoos, usesBallparkFor, home games]
-
A.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
B.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
C.
sharesBallparkWith
Indicates that two entities use or occupy the same ballpark as their home or primary venue.
-
D.
associatedWithBallpark
Indicates that an entity has a relationship or connection to a specific ballpark, such as location, operation, or affiliation.
-
E.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
- F. None of above. chosen
Provenance (4 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb2277a48190ae7594c4c4965a01 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.