Triple
T24903369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newmarket Handicap |
E623637
|
entity |
| Predicate | typicalStartType |
P177275
|
FINISHED |
| Object | barrier start |
—
|
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: barrier start | Statement: [Newmarket Handicap, typicalStartType, barrier start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartType Context triple: [Newmarket Handicap, typicalStartType, barrier start]
-
A.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
C.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
D.
traditionalStart
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
E.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 18, 2026, 5:27 a.m.