Triple
T1185767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Division |
E25241
|
entity |
| Predicate | establishedInLeagueRealignment |
P3196
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Northwest Division, establishedInLeagueRealignment, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedInLeagueRealignment Context triple: [Northwest Division, establishedInLeagueRealignment, 2004]
-
A.
establishedInLeague
Indicates that an entity (such as a team or club) was founded or formally created while participating in, or as part of, a particular league.
-
B.
divisionRealignment
chosen
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
C.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
D.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
-
E.
movedToLeague
Indicates that an entity changed affiliation or membership from one league to another.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.