Triple
T22310800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carter Handicap |
E551505
|
entity |
| Predicate | raceTypeOfWeights |
P49218
|
FINISHED |
| Object | handicap |
—
|
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: handicap | Statement: [Carter Handicap, raceTypeOfWeights, handicap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceTypeOfWeights Context triple: [Carter Handicap, raceTypeOfWeights, handicap]
-
A.
raceTypeStrength
Indicates the degree or category of physical or competitive strength associated with a particular race type in the relationship.
-
B.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
C.
raceTypeDetail
chosen
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
D.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
E.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574e7fc0819080e3e85001ab2c90 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.