Triple
T12211217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Cardinals (NFL) 1965 |
E290962
|
entity |
| Predicate | seasonNumberInStLouis |
P103817
|
FINISHED |
| Object | 6th season in St. Louis |
—
|
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: 6th season in St. Louis | Statement: [St. Louis Cardinals (NFL) 1965, seasonNumberInStLouis, 6th season in St. Louis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonNumberInStLouis Context triple: [St. Louis Cardinals (NFL) 1965, seasonNumberInStLouis, 6th season in St. Louis]
-
A.
seasonNumberInYear
Indicates the specific ordinal position of a season within a given year.
-
B.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
C.
seasonNumberInConferenceHistory
Indicates the ordinal number of a particular season within the overall chronological history of a conference.
-
D.
leagueSeasonNumber
Indicates the ordinal number assigned to a particular season within a league’s sequence of seasons.
-
E.
franchiseSeasonNumber
Indicates the specific season number assigned to an installment within a larger franchise series.
- F. None of above. chosen
Provenance (4 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d920c3dc9881908c396a4ab34f4836 |
completed | April 10, 2026, 4:09 p.m. |
Created at: April 8, 2026, 9:51 p.m.