Triple
T23623671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMD Motorsports |
E583396
|
entity |
| Predicate | targetDrivers |
P152158
|
FINISHED |
| Object | junior open-wheel drivers |
—
|
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: junior open-wheel drivers | Statement: [HMD Motorsports, targetDrivers, junior open-wheel drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDrivers Context triple: [HMD Motorsports, targetDrivers, junior open-wheel drivers]
-
A.
developedDriversFor
Indicates that one entity created or produced software drivers to enable another entity’s hardware or system to function or be controlled.
-
B.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
C.
driverFor
Indicates that one entity serves as the driver or operator of a vehicle or transport service for another entity.
-
D.
drivers
Indicates that one entity operates or controls a vehicle or means of transport for another entity or in a given context.
-
E.
driversInField
chosen
Indicates that certain drivers are currently present, active, or operating within a specified field or area.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17be6288190a409df700c1003bd |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.