Triple
T35968711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Repole |
E1040216
|
entity |
| Predicate | typeOfHorseRacingInvolvement |
P108046
|
FINISHED |
| Object | thoroughbred racing |
—
|
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: thoroughbred racing | Statement: [Mike Repole, typeOfHorseRacingInvolvement, thoroughbred racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHorseRacingInvolvement Context triple: [Mike Repole, typeOfHorseRacingInvolvement, thoroughbred racing]
-
A.
hasMotorsportInvolvement
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
B.
hasRacingDiscipline
chosen
Indicates that an entity participates in, is associated with, or is characterized by a specific type or category of racing discipline.
-
C.
usesHorseType
Indicates that one entity employs, relies on, or operates using a specific type or category of horse.
-
D.
ownedRacehorse
Indicates that one entity possessed legal ownership of a particular racehorse.
-
E.
raceTypeHosted
Indicates that a particular type of race is organized or held by a given host or organizing entity.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
Created at: May 3, 2026, 4:07 p.m.