Triple
T38223014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Rams, 1998–2001 |
E1012061
|
entity |
| Predicate | regularSeasonRecord2000 |
P21379
|
FINISHED |
| Object | 10–6 |
—
|
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: 10–6 | Statement: [St. Louis Rams, 1998–2001, regularSeasonRecord2000, 10–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonRecord2000 Context triple: [St. Louis Rams, 1998–2001, regularSeasonRecord2000, 10–6]
-
A.
regularSeasonRecord2001
Indicates the win-loss (and possibly tie) record an entity achieved during the 2001 regular season.
-
B.
regularSeasonRecord2020
Indicates the win-loss (and possibly tie) record an entity achieved during the 2020 regular season.
-
C.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
D.
bestRegularSeasonRecordYear
Indicates the year in which an entity achieved its best regular-season record compared to all its other seasons.
-
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:30 p.m.