Triple
T3515474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turner Field |
E74296
|
entity |
| Predicate | convertedToBaseballStadium |
P48473
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Turner Field, convertedToBaseballStadium, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToBaseballStadium Context triple: [Turner Field, convertedToBaseballStadium, 1997]
-
A.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
B.
movedToCurrentBallpark
Indicates that an entity (typically a sports team) relocated its home games to its current ballpark or stadium.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
homeBaseballField
Indicates that one entity serves as the primary or designated baseball field used as the home venue by the other entity.
-
E.
ballparkFormerName
Indicates that one name was previously used as the official name of a particular ballpark before it was changed.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc30362c81908ca7497a6a935cc6 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.