Triple
T980614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Mariners |
E21157
|
entity |
| Predicate | bestRegularSeasonWinsSeason |
P16717
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Seattle Mariners, bestRegularSeasonWinsSeason, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestRegularSeasonWinsSeason Context triple: [Seattle Mariners, bestRegularSeasonWinsSeason, 2001]
-
A.
regularSeasonWins
Indicates the number of games a team wins during the regular season of a competition.
-
B.
bestRegularSeasonRecord
Indicates that an entity (typically a team) achieved the highest overall performance record during the regular season compared to all others in the same competition.
-
C.
bestRegularSeasonRecordYear
chosen
Indicates the year in which an entity achieved its best regular-season record compared to all its other seasons.
-
D.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
E.
championRegularSeasonRecord
Indicates that an entity is the champion associated with a particular regular season record.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47b58ec81908d95f151b9af3dae |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.