Triple
T17473464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee Petty |
E425475
|
entity |
| Predicate | racingStyle |
P56420
|
FINISHED |
| Object | consistent points racer |
—
|
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: consistent points racer | Statement: [Lee Petty, racingStyle, consistent points racer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingStyle Context triple: [Lee Petty, racingStyle, consistent points racer]
-
A.
styleOfRacing
chosen
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
B.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
C.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
D.
racingDivision
Indicates that one entity is classified into, or associated with, a particular racing division within a competitive racing context.
-
E.
racingNumber
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451b990848190b2e8510d67e94b79 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.