Triple
T25796136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coventry Stakes |
E649687
|
entity |
| Predicate | scheduledMeetingDay |
P26202
|
FINISHED |
| Object | first day of Royal Ascot |
—
|
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: first day of Royal Ascot | Statement: [Coventry Stakes, scheduledMeetingDay, first day of Royal Ascot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledMeetingDay Context triple: [Coventry Stakes, scheduledMeetingDay, first day of Royal Ascot]
-
A.
meetingDay
chosen
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
-
B.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
C.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
D.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
E.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:30 a.m.