Triple
T19971782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morecambe Missile |
E480093
|
entity |
| Predicate | associatedRaceType |
P118441
|
FINISHED |
| Object | time-trial motorcycle 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: time-trial motorcycle races | Statement: [Morecambe Missile, associatedRaceType, time-trial motorcycle races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRaceType Context triple: [Morecambe Missile, associatedRaceType, time-trial motorcycle races]
-
A.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
B.
associatedWithRaceCategory
chosen
Indicates a relationship in which an entity is linked or assigned to a particular race category.
-
C.
hasAssociatedRace
Indicates that an entity is linked to or characterized by a particular race or racial classification.
-
D.
hasRace
Indicates that an entity possesses or is characterized by a particular race or racial classification.
-
E.
playableRace
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc9694881909a31841702ab9e5f |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.