Triple
T30026616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 300 Series |
E762896
|
entity |
| Predicate | driverModel |
P170441
|
FINISHED |
| Object | Nvidia ForceWare |
—
|
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: Nvidia ForceWare | Statement: [GeForce 300 Series, driverModel, Nvidia ForceWare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driverModel Context triple: [GeForce 300 Series, driverModel, Nvidia ForceWare]
-
A.
driverType
Indicates the category or role of a driver associated with an entity or activity (e.g., primary, backup, commercial, etc.).
-
B.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
D.
driverFor
Indicates that one entity serves as the driver or operator of a vehicle or transport service for another entity.
-
E.
driveModes
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 6:48 p.m.