Triple
T29165811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Major League Baseball season |
E739313
|
entity |
| Predicate | winsLeader_NL |
P78187
|
FINISHED |
| Object | Tom Glavine |
—
|
NE NERFINISHED |
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: Tom Glavine | Statement: [2000 Major League Baseball season, winsLeader_NL, Tom Glavine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winsLeader_NL Context triple: [2000 Major League Baseball season, winsLeader_NL, Tom Glavine]
-
A.
winsLeader
Indicates that one entity achieves victory or leadership over another in a competitive or comparative context.
-
B.
pennantWinnerNL
Indicates that a team has won the National League pennant in a given baseball season.
-
C.
leagueLeaderIn
chosen
Indicates that an entity is the current top-ranked or leading participant within a specified league or competition.
-
D.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
E.
hitsLeader
Indicates that an entity performs a hitting action on another entity who is in a leader role.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d4efc88190a18d80abadc96faf |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:49 a.m.