Triple
T17243368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterling Marlin |
E418556
|
entity |
| Predicate | knownForDrivingStyle |
P92948
|
FINISHED |
| Object | smooth and consistent on superspeedways |
—
|
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: smooth and consistent on superspeedways | Statement: [Sterling Marlin, knownForDrivingStyle, smooth and consistent on superspeedways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForDrivingStyle Context triple: [Sterling Marlin, knownForDrivingStyle, smooth and consistent on superspeedways]
-
A.
hasDrivingStyle
chosen
Indicates the characteristic manner or pattern in which an entity typically drives.
-
B.
drivingCharacter
Indicates that one character is operating or controlling a vehicle or mode of transportation.
-
C.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
D.
drivingExperience
Indicates the extent or history of a person's involvement in driving vehicles, typically measured by duration, frequency, or level of skill.
-
E.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e21bb5c8190ad960f231fe54665 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.