Triple
T6735729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohokam Stadium |
E153748
|
entity |
| Predicate | springTrainingHomeFrom |
P1744
|
FINISHED |
| Object | Chicago Cubs 1997–2013 |
—
|
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: Chicago Cubs 1997–2013 | Statement: [Hohokam Stadium, springTrainingHomeFrom, Chicago Cubs 1997–2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: springTrainingHomeFrom Context triple: [Hohokam Stadium, springTrainingHomeFrom, Chicago Cubs 1997–2013]
-
A.
springTrainingLocation
chosen
Indicates the location where an entity conducts its spring training activities.
-
B.
springTrainingHistory
Indicates the historical record of an entity’s participation, events, or performance during spring training periods.
-
C.
springTrainingTeam
Indicates that a team is participating as a designated club in Major League Baseball spring training activities.
-
D.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
-
E.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18369d88190a73349075462202b |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:09 p.m.