Triple
T29677019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA Optimus |
E750843
|
entity |
| Predicate | successorOrVariant |
P16897
|
FINISHED |
| Object | NVIDIA Advanced Optimus |
—
|
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 Advanced Optimus | Statement: [NVIDIA Optimus, successorOrVariant, NVIDIA Advanced Optimus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOrVariant Context triple: [NVIDIA Optimus, successorOrVariant, NVIDIA Advanced Optimus]
-
A.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
B.
successorModel
chosen
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
C.
successorInstanceOf
Indicates that one entity is a later or updated instance of another, preserving a continuity or versioned succession between them.
-
D.
successorOrComplement
Indicates that one entity either directly follows another in a sequence or serves as its logical or functional complement.
-
E.
introducedAsSuccessorOf
Indicates that one entity was formally presented or designated to take over the role, position, or function previously held by another entity.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 28, 2026, 7:07 p.m.