Triple
T18318224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godolphin Stables, Newmarket |
E438801
|
entity |
| Predicate | hasTrainingSeason |
P49132
|
FINISHED |
| Object | flat racing season |
—
|
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: flat racing season | Statement: [Godolphin Stables, Newmarket, hasTrainingSeason, flat racing season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingSeason Context triple: [Godolphin Stables, Newmarket, hasTrainingSeason, flat racing season]
-
A.
trainingSeason
chosen
Indicates the specific season or time period during which training activities or programs take place.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
D.
hasFieldSeason
Indicates that an entity is associated with a specific field season during which related activities, observations, or operations take place.
-
E.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa342a881909afcd995405027af |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.