Triple
T31047863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Boston Speedway |
E791175
|
entity |
| Predicate | hasTypicalRaceDistance |
P125380
|
FINISHED |
| Object | short-track feature events |
—
|
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: short-track feature events | Statement: [South Boston Speedway, hasTypicalRaceDistance, short-track feature events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalRaceDistance Context triple: [South Boston Speedway, hasTypicalRaceDistance, short-track feature events]
-
A.
typicalRaceLengthCategory
chosen
Indicates the usual distance range or length classification that a race is most commonly run at.
-
B.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
-
C.
majorRaceDistance
Indicates the standard or primary distance over which a major race or competition is contested.
-
D.
raceDistanceType
Indicates the specific type or category of distance over which a race is conducted.
-
E.
typicalRaceDistanceLaps
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
- 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_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 29, 2026, 9 p.m.