Triple
T17249674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 Major League Baseball season |
E418717
|
entity |
| Predicate | teamWinsRecord |
P14130
|
FINISHED |
| Object | Seattle Mariners 116 wins |
—
|
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: Seattle Mariners 116 wins | Statement: [2001 Major League Baseball season, teamWinsRecord, Seattle Mariners 116 wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamWinsRecord Context triple: [2001 Major League Baseball season, teamWinsRecord, Seattle Mariners 116 wins]
-
A.
mostOverallWinsRecord
Indicates that the subject holds the record for having the greatest total number of wins compared to all others in the relevant context.
-
B.
seasonRecordWins
chosen
Indicates the number of games a team has won during a specific season.
-
C.
winnerSeriesRecord
Indicates that one entity holds a winning record over another entity across a series of contests or events.
-
D.
managerialRecordWins
Indicates the number of wins credited to an individual in their role as a manager or head coach.
-
E.
teamRecord
Indicates the recorded performance statistics (such as wins, losses, and ties) associated with a particular team over a defined period or competition.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e2636f48190b29548ff80402bef |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.