Triple
T22107107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remsen Stakes |
E546313
|
entity |
| Predicate | typicalTrackCondition |
P147008
|
FINISHED |
| Object | fast |
—
|
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: fast | Statement: [Remsen Stakes, typicalTrackCondition, fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrackCondition Context triple: [Remsen Stakes, typicalTrackCondition, fast]
-
A.
typicalTrackCharacteristics
Indicates that the associated characteristics represent the usual or standard features of a given track.
-
B.
typicalTrackCode
Indicates that one entity is the standard or commonly used track code associated with another entity.
-
C.
standardTrackStatus
Indicates the current state or phase of a track within a standardized processing, review, or lifecycle workflow.
-
D.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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.