Triple
T35484112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHA Midwest Division |
E1025543
|
entity |
| Predicate | dissolvedInLeagueRealignment |
P3196
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WHA Midwest Division, dissolvedInLeagueRealignment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedInLeagueRealignment Context triple: [WHA Midwest Division, dissolvedInLeagueRealignment, true]
-
A.
leagueDissolutionContext
Indicates the circumstances or reasons under which a league is dissolved or ceases to exist.
-
B.
divisionRealignment
chosen
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
C.
leagueDisbanded
Indicates that a sports league or competitive organization has formally ceased operations and no longer exists as an active entity.
-
D.
rejoinedLeagueName
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
E.
reorganizedAsModernLeague
Indicates that an earlier or traditional league structure was restructured or reconstituted into a modern league format.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.