Triple
T18111068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Champions Fillies and Mares Stakes |
E433473
|
entity |
| Predicate | inauguratedAsGroupRace |
P130490
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [British Champions Fillies and Mares Stakes, inauguratedAsGroupRace, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguratedAsGroupRace Context triple: [British Champions Fillies and Mares Stakes, inauguratedAsGroupRace, 2011]
-
A.
inauguratedAsInternationalRace
Indicates that an event or competition was officially established or launched with the status of an international race.
-
B.
isInauguralRace
Indicates that the race is the first-ever or opening event in a series, season, or competition.
-
C.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
D.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
E.
hasRaceNamedAfter
Indicates that an entity has a race or competition that is named in honor of, or after, another entity.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.