Triple
T30961714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Course |
E788842
|
entity |
| Predicate | usedForRaceType |
P120070
|
FINISHED |
| Object | hurdle races |
—
|
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: hurdle races | Statement: [New Course, usedForRaceType, hurdle races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForRaceType Context triple: [New Course, usedForRaceType, hurdle races]
-
A.
inUseAsRaceClubUntil
Indicates that something continued to function as a race club up to a specified time or date.
-
B.
hasRaceDayType
Indicates the specific category or type assigned to a race day (e.g., practice, qualifying, main event) within a schedule or event structure.
-
C.
hasRacingUseSince
Indicates that an entity has been used for racing starting from a specified point in time.
-
D.
hasRaceFormat
chosen
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
E.
appearsInRace
Indicates that an entity participates as a competitor or entrant in a specific race event.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:54 p.m.