Triple

T18110576
Position Surface form Disambiguated ID Type / Status
Subject Epsom Oaks E433461 entity
Predicate typicalScheduleRelation P3309 FINISHED
Object run on the day before the Derby or during the Derby Festival 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: run on the day before the Derby or during the Derby Festival | Statement: [Epsom Oaks, typicalScheduleRelation, run on the day before the Derby or during the Derby Festival]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalScheduleRelation
Context triple: [Epsom Oaks, typicalScheduleRelation, run on the day before the Derby or during the Derby Festival]
  • A. originalScheduleRelation
    Indicates a relationship where one schedule is defined as the original or baseline reference for another schedule or scheduling state.
  • B. typicalSchedule chosen
    Indicates the usual or standard timing and sequence of activities or events associated with an entity.
  • C. typicalEndRelation
    Indicates that one event, state, or process is the usual or characteristic endpoint or outcome of another.
  • D. seriesRelation
    Indicates a relationship where one entity is part of, follows from, or is otherwise connected to another within an ordered series or sequence.
  • E. stageRelation
    Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd2038081909515fb6d17495cbf completed April 19, 2026, 1:51 p.m.
PD Predicate disambiguation batch_69e43313ca788190baa224269e71de49 completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:28 a.m.