Triple
T17704799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge May Bumps |
E441401
|
entity |
| Predicate | schedulePattern |
P128659
|
FINISHED |
| Object | raced over consecutive weekdays |
—
|
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: raced over consecutive weekdays | Statement: [Cambridge May Bumps, schedulePattern, raced over consecutive weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulePattern Context triple: [Cambridge May Bumps, schedulePattern, raced over consecutive weekdays]
-
A.
shiftPattern
Indicates a recurring schedule or arrangement that defines how work or activity shifts are organized over time.
-
B.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
C.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
D.
workPattern
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
E.
scheduleUsage
Indicates how and when a schedule is applied or utilized in relation to associated entities or events.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47296770c8190b6b172fb647da564 |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d018227c8190b6624a2199e765e8 |
completed | April 18, 2026, 6:40 p.m. |
Created at: April 10, 2026, 10:05 a.m.