Triple
T7463691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacing Triple Crown |
E176316
|
entity |
| Predicate | componentRaceClass |
P10053
|
FINISHED |
| Object | classic race |
—
|
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: classic race | Statement: [Pacing Triple Crown, componentRaceClass, classic race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentRaceClass Context triple: [Pacing Triple Crown, componentRaceClass, classic race]
-
A.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
-
B.
notableRaceClass
Indicates that there exists a notable race or competition of a particular class or category associated with the subject.
-
C.
competitionClass
chosen
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
D.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
E.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d9d25c819087efc772b5b127fa |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.