Triple
T21411471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripon Racecourse |
E528180
|
entity |
| Predicate | hasNotableRaceMonth |
P143862
|
FINISHED |
| Object | August |
—
|
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: August | Statement: [Ripon Racecourse, hasNotableRaceMonth, August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRaceMonth Context triple: [Ripon Racecourse, hasNotableRaceMonth, August]
-
A.
hasNotableRace
Indicates that an entity is associated with a race or competition that is considered notable or significant.
-
B.
hasRaceWeek
Indicates that a particular time period is designated as the week during which a race event takes place.
-
C.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
D.
hasNotabilityPeriod
Indicates the time span during which an entity is or was notable or prominent.
-
E.
hasNotableYear
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1fe2cd08190bfaf28daae4f5233 |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:43 p.m.