Triple
T1491717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Target Field |
E29593
|
entity |
| Predicate | distanceFromPreviousBallpark |
P21270
|
FINISHED |
| Object | approximately 0.5 miles from the Metrodome |
—
|
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: approximately 0.5 miles from the Metrodome | Statement: [Target Field, distanceFromPreviousBallpark, approximately 0.5 miles from the Metrodome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPreviousBallpark Context triple: [Target Field, distanceFromPreviousBallpark, approximately 0.5 miles from the Metrodome]
-
A.
movedToCurrentBallpark
Indicates that an entity (typically a sports team) relocated its home games to its current ballpark or stadium.
-
B.
distanceToSuccessorStadium
chosen
Indicates the measured distance between a stadium and the stadium that directly succeeds it in a defined sequence or timeline.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
E.
distanceToHomePlate
Indicates the measured distance between an entity’s current position and home plate.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c3ace4819081bc2b86ee2486b6 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.