Triple
T2855461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Division (NHL) |
E63188
|
entity |
| Predicate | teamRelocation |
P36297
|
FINISHED |
| Object | Atlanta Thrashers to Winnipeg Jets in 2011 |
—
|
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 in 2011 | Statement: [Southeast Division (NHL), teamRelocation, Atlanta Thrashers to Winnipeg Jets in 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRelocation Context triple: [Southeast Division (NHL), teamRelocation, Atlanta Thrashers to Winnipeg Jets in 2011]
-
A.
teamRelocationTo
chosen
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
-
C.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
D.
cityLosingFranchise
Indicates that a city is losing, or has lost, a professional sports franchise or major team based there.
-
E.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf60852c8190b66c8719c63a723e |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.