Triple
T20883428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Sting |
E514208
|
entity |
| Predicate | indoorLeagueStatus |
P67126
|
FINISHED |
| Object | defunct MISL franchise |
—
|
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: defunct MISL franchise | Statement: [Chicago Sting, indoorLeagueStatus, defunct MISL franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorLeagueStatus Context triple: [Chicago Sting, indoorLeagueStatus, defunct MISL franchise]
-
A.
traditionalLeagueStatus
Indicates whether an entity holds a historically established or customary status within a particular league or competitive organization.
-
B.
associatedLeagueStatus
chosen
Indicates that there exists a relationship specifying the league-related status or standing of an associated entity within a particular league context.
-
C.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
D.
parentLeagueStatus
Indicates the status or condition of a league in relation to its parent league or overarching league structure.
-
E.
men'sLeagueStatus
Indicates the competitive or organizational status of a men's league within a given sport or system.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67b03088190be7cbcde8c59509a |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.