Triple
T488592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Division |
E9934
|
entity |
| Predicate | formerTeamRelocation |
P14055
|
FINISHED |
| Object | Atlanta Thrashers to Winnipeg Jets |
—
|
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: Atlanta Thrashers to Winnipeg Jets | Statement: [Southeast Division, formerTeamRelocation, Atlanta Thrashers to Winnipeg Jets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTeamRelocation Context triple: [Southeast Division, formerTeamRelocation, Atlanta Thrashers to Winnipeg Jets]
-
A.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
B.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
C.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
D.
previousTeamNamesAlsoAssociatedWithFranchise
Indicates that the earlier team names are also historically or officially linked to the same franchise.
-
E.
formerSportsTeam
Indicates that an entity was once a member of or played for a particular sports team in the past but no longer does so.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0df764481909811d9483dfbc4aa |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.