Triple
T21120252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane Empire |
E520408
|
entity |
| Predicate | regularSeasonRecord2017 |
P21379
|
FINISHED |
| Object | 8–8 |
—
|
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: 8–8 | Statement: [Spokane Empire, regularSeasonRecord2017, 8–8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonRecord2017 Context triple: [Spokane Empire, regularSeasonRecord2017, 8–8]
-
A.
awayTeamRegularSeasonRecord
Indicates the win-loss (and possibly tie) record that the away team has accumulated during the regular season.
-
B.
ALTeamRegularSeasonRecord
Indicates the relationship that specifies a team's win–loss record during the American League regular season.
-
C.
regularSeasonRecord1967–68
Indicates the win-loss (and possibly tie) performance of a team during the 1967–68 regular season.
-
D.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
E.
NLTeamRegularSeasonRecord
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72233a43481909535560514d388be |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:55 p.m.