Triple
T31047867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Boston Speedway |
E791175
|
entity |
| Predicate | hasPrimaryRacingCategory |
P49213
|
FINISHED |
| Object | late model stock cars |
—
|
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: late model stock cars | Statement: [South Boston Speedway, hasPrimaryRacingCategory, late model stock cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRacingCategory Context triple: [South Boston Speedway, hasPrimaryRacingCategory, late model stock cars]
-
A.
hasRacingDiscipline
Indicates that an entity participates in, is associated with, or is characterized by a specific type or category of racing discipline.
-
B.
hasRacingCode
Indicates that an entity is associated with a specific racing classification or identifier code.
-
C.
hasRaceClass
chosen
Indicates that an entity participates in or is associated with a particular race classification or category.
-
D.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
E.
hasRaceDayType
Indicates the specific category or type assigned to a race day (e.g., practice, qualifying, main event) within a schedule or event structure.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: April 29, 2026, 9 p.m.