Triple
T26229431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinsville Speedway |
E655987
|
entity |
| Predicate | isOnScheduleOf |
P14477
|
FINISHED |
| Object | NASCAR Cup Series |
—
|
NE NERFINISHED |
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: NASCAR Cup Series | Statement: [Martinsville Speedway, isOnScheduleOf, NASCAR Cup Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnScheduleOf Context triple: [Martinsville Speedway, isOnScheduleOf, NASCAR Cup Series]
-
A.
containsSchedule
chosen
Indicates that one entity includes or holds a schedule associated with another entity or activity.
-
B.
hasPerformanceSchedule
Indicates that an entity has an associated timetable or plan specifying when its performances or shows are scheduled to occur.
-
C.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
D.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
E.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d56b0388190826b97fa17dc97ce |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:59 p.m.