Triple
T6173064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Dixon |
E137748
|
entity |
| Predicate | hasDriverCategory |
P69218
|
FINISHED |
| Object | professional racing driver |
—
|
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: professional racing driver | Statement: [Scott Dixon, hasDriverCategory, professional racing driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriverCategory Context triple: [Scott Dixon, hasDriverCategory, professional racing driver]
-
A.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
B.
allowsCupDrivers
Indicates that one entity grants permission or authorization for Cup drivers to participate in or make use of another entity.
-
C.
driverRequirement
Indicates that a certain driver, qualification, or driving-related condition is required for an entity to perform or be associated with a particular role, task, or operation.
-
D.
supportsRiderCategory
Indicates that one entity is capable of accommodating, enabling, or being compatible with a specified rider category.
-
E.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
- F. None of above. chosen
Provenance (4 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.