Triple
T24903399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning Stakes |
E623638
|
entity |
| Predicate | raceClassUpgradedToGroup1 |
P96864
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Lightning Stakes, raceClassUpgradedToGroup1, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceClassUpgradedToGroup1 Context triple: [Lightning Stakes, raceClassUpgradedToGroup1, 1980]
-
A.
upgradedToGroup1
chosen
Indicates that an entity has been elevated or transitioned to a higher-status category or group labeled "Group 1".
-
B.
upgradedToGroup1From
Indicates that an entity has been elevated or transitioned into group 1 status from another specified source group or category.
-
C.
formerRaceGrade
Indicates that an entity previously held a certain race grade or classification but no longer does.
-
D.
inauguratedAsGroupRace
Indicates that an event or competition was officially initiated or first held in the format of a group race.
-
E.
upgradedToGroup3
Indicates that an entity has been changed or elevated from its previous status or category to membership in group 3.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.