Triple
T24587691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champion Hurdle |
E608441
|
entity |
| Predicate | isChampionshipRaceFor |
P10813
|
FINISHED |
| Object | two-mile hurdlers |
—
|
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: two-mile hurdlers | Statement: [Champion Hurdle, isChampionshipRaceFor, two-mile hurdlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChampionshipRaceFor Context triple: [Champion Hurdle, isChampionshipRaceFor, two-mile hurdlers]
-
A.
isSprintChampionshipRace
Indicates that the race is designated as the sprint championship event within a competition or season.
-
B.
championshipFor
chosen
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
C.
championshipSeries
Indicates a competitive series of contests or games that determines a champion between qualifying participants.
-
D.
containsChampionshipCourse
Indicates that an entity includes or features a golf course that meets recognized championship-level standards.
-
E.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9898f708190b521317207c79f64 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.