Triple
T6021523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR Pinty’s Series |
E134075
|
entity |
| Predicate | typicalRaceFormat |
P49218
|
FINISHED |
| Object | sprint and mid-distance 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: sprint and mid-distance events | Statement: [NASCAR Pinty’s Series, typicalRaceFormat, sprint and mid-distance events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceFormat Context triple: [NASCAR Pinty’s Series, typicalRaceFormat, sprint and mid-distance events]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
C.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
D.
raceTypeDetail
chosen
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
E.
stageRaceType
Indicates the specific category or format of a multi-stage race within a broader competition or event.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fba86a48190984e95d5adf7c7f1 |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.