Triple
T24688116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 National League Championship Series |
E611352
|
entity |
| Predicate | teamChampionDivision |
P43565
|
FINISHED |
| Object | National League West |
—
|
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: National League West | Statement: [1976 National League Championship Series, teamChampionDivision, National League West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamChampionDivision Context triple: [1976 National League Championship Series, teamChampionDivision, National League West]
-
A.
leagueChampionTeam
Indicates that a given team is the champion (winner) of a specified league or league season.
-
B.
divisionChampionChampionTeam
chosen
Indicates that a particular team is the champion of a specific division in a competition or league.
-
C.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
D.
opponentLeagueChampionTeam
Indicates that a team is the league champion team that an opponent team competes against.
-
E.
team1Division
Indicates the competitive division or grouping in which the first team participates or is classified.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:19 a.m.