Triple
T17249611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 American League Championship Series |
E418716
|
entity |
| Predicate | regularSeasonWinsTeam2 |
P14873
|
FINISHED |
| Object | 116 |
—
|
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: 116 | Statement: [2001 American League Championship Series, regularSeasonWinsTeam2, 116]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonWinsTeam2 Context triple: [2001 American League Championship Series, regularSeasonWinsTeam2, 116]
-
A.
regularSeasonWins
chosen
Indicates the number of games a team wins during the regular season of a competition.
-
B.
regularSeasonWinsRecordNote
Indicates a note or special remark associated with an entity’s regular season wins record, such as exceptions, conditions, or clarifications about how that record was achieved or recorded.
-
C.
bestRegularSeasonWins
Indicates the number of wins a team achieved in its most successful regular season.
-
D.
regularSeasonFirstPlaceTeam
Indicates the team that finished in first place in the standings at the end of the regular season.
-
E.
winningTeamFranchise
Indicates the franchise to which the team that won a given game, event, or competition belongs.
- 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_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.