Triple
T21175037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hut Stricklin |
E521788
|
entity |
| Predicate | yearOfBestCupSeriesPointsPosition |
P105795
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Hut Stricklin, yearOfBestCupSeriesPointsPosition, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfBestCupSeriesPointsPosition Context triple: [Hut Stricklin, yearOfBestCupSeriesPointsPosition, 1991]
-
A.
bestCupSeasonPointsYear
Indicates the year in which an entity achieved its highest total of Cup season points.
-
B.
bestConstructorsChampionshipPosition
Indicates the highest (best) finishing position a constructor has achieved in a constructors’ championship standings.
-
C.
rankInAllTimeCupSeriesWins
Indicates the position an entity holds in the ordered list of all-time total wins in a particular cup series.
-
D.
NASCARCupSeriesBestPointsFinishSeason
chosen
Indicates the season in which an entity achieved its highest-ever points finish in the NASCAR Cup Series standings.
-
E.
bestFormulaOneChampionshipPosition
Indicates the highest (best) finishing position an entity has ever achieved in a Formula One World Championship season.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7271597288190b04baff9ca8d866c |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.