Triple
T13509342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lent Bumps |
E321094
|
entity |
| Predicate | raceSchedule |
P96554
|
FINISHED |
| Object | multiple divisions racing on each day |
—
|
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: multiple divisions racing on each day | Statement: [Lent Bumps, raceSchedule, multiple divisions racing on each day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSchedule Context triple: [Lent Bumps, raceSchedule, multiple divisions racing on each day]
-
A.
racesOn
Indicates that one entity participates in a race or competitive running event that takes place on or along another entity (such as a track, course, or surface).
-
B.
seasonSchedule
Indicates the planned timing and sequence of events, activities, or occurrences within a specific season.
-
C.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
D.
showSchedule
Indicates that an entity presents or displays a timetable or planned sequence of events for another entity.
-
E.
competitionCalendar
chosen
Indicates that there is a scheduled set of competitive events or matches associated with an entity over a defined period.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.