Triple
T1322437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Rockies |
E28248
|
entity |
| Predicate | previousHomeFieldYears |
P26518
|
FINISHED |
| Object | 1993–1994 |
—
|
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: 1993–1994 | Statement: [Colorado Rockies, previousHomeFieldYears, 1993–1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomeFieldYears Context triple: [Colorado Rockies, previousHomeFieldYears, 1993–1994]
-
A.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
B.
homeTeamSince
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
C.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
D.
formerHomeArena
Indicates that a venue previously served as the primary home arena for a team or organization but no longer holds that status.
-
E.
precededByHomeStadium
Indicates that one entity’s existence, use, or designation as a home stadium occurred earlier in time than another home stadium associated with the same team or organization.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19b76b48190aa8857b80971a842 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:55 p.m.