Triple
T20883417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Sting |
E514208
|
entity |
| Predicate | indoorLeagueExit |
P69105
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Chicago Sting, indoorLeagueExit, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorLeagueExit Context triple: [Chicago Sting, indoorLeagueExit, 1988]
-
A.
losingLeague
Indicates that a league is in a losing or disadvantaged position, such as having an overall negative performance or being behind its competitors.
-
B.
losingLeagueRepresentative
Indicates that an entity serves as the representative of the league that lost in a particular competition or matchup.
-
C.
losingLeagueTeam
Indicates that a team is the one that lost in a particular league game or competition.
-
D.
teamEliminated
chosen
Indicates that a team has been removed from further participation or contention in a competition, tournament, or series.
-
E.
stadiumEndType
Indicates the type or manner in which a stadium’s structure or boundary terminates at its ends (e.g., open, closed, rounded).
- 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.