Triple
T17829719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Jubilee Stakes |
E445218
|
entity |
| Predicate | timingWithinMeeting |
P80406
|
FINISHED |
| Object | final 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: final day of Royal Ascot | Statement: [Diamond Jubilee Stakes, timingWithinMeeting, final day of Royal Ascot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingWithinMeeting Context triple: [Diamond Jubilee Stakes, timingWithinMeeting, final day of Royal Ascot]
-
A.
meetingState
Indicates the current status or phase of a meeting within its overall lifecycle (e.g., scheduled, in progress, or completed).
-
B.
meetingPeriod
chosen
Indicates the time span or duration during which a meeting takes place.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
-
E.
meetsWhen
Indicates that two entities come together or encounter each other at a specific time or under particular temporal conditions.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48917c4d88190b919a4b75aed011c |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.