Triple
T22450689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Risen Star Stakes |
E554979
|
entity |
| Predicate | timingRelativeToDerby |
P148247
|
FINISHED |
| Object | Held several months before the Kentucky Derby |
—
|
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: Held several months before the Kentucky Derby | Statement: [Risen Star Stakes, timingRelativeToDerby, Held several months before the Kentucky Derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingRelativeToDerby Context triple: [Risen Star Stakes, timingRelativeToDerby, Held several months before the Kentucky Derby]
-
A.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
B.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
C.
timingProvider
Indicates that one entity serves as the source or controller of timing information or synchronization for another entity.
-
D.
migrationTiming
Indicates the temporal characteristics or schedule of when a migration event occurs or is expected to occur.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ba6a88190a0a79e2c20fa8c08 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:48 p.m.