Triple
T7875219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Racecourse |
E182833
|
entity |
| Predicate | hasRacingSeason |
P55487
|
FINISHED |
| Object | primarily April to October |
—
|
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: primarily April to October | Statement: [Windsor Racecourse, hasRacingSeason, primarily April to October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRacingSeason Context triple: [Windsor Racecourse, hasRacingSeason, primarily April to October]
-
A.
hasRaceWeek
Indicates that a particular time period is designated as the week during which a race event takes place.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
racingPeriod
chosen
Indicates the time span during which a racing event or competition takes place.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a961188190b2f12f8fe5d66641 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.