Triple
T22107100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remsen Stakes |
E546313
|
entity |
| Predicate | roleInRacingCalendar |
P147007
|
FINISHED |
| Object | early Kentucky Derby prep |
—
|
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: early Kentucky Derby prep | Statement: [Remsen Stakes, roleInRacingCalendar, early Kentucky Derby prep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRacingCalendar Context triple: [Remsen Stakes, roleInRacingCalendar, early Kentucky Derby prep]
-
A.
roleInFormulaE
Indicates that an entity holds a specific role or position within the context of Formula E.
-
B.
motorsportRole
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
-
C.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
D.
motorsportHomologationRole
Indicates the specific role or function an entity has within the homologation (official approval and certification) process in motorsport.
-
E.
sportingRoleRecognised
Indicates that a particular sporting role or position has been formally acknowledged or accepted as valid within a given context or system.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12919dd388190b8ca08e2464cb0b8 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:30 p.m.