Triple
T30134362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 16 Series |
E765943
|
entity |
| Predicate | doesNotUseBranding |
P2558
|
FINISHED |
| Object | GeForce RTX |
—
|
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: GeForce RTX | Statement: [GeForce 16 Series, doesNotUseBranding, GeForce RTX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotUseBranding Context triple: [GeForce 16 Series, doesNotUseBranding, GeForce RTX]
-
A.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
B.
hasNotableBrandAssociation
Indicates that there is a significant, recognizable, or influential brand linked or connected to the subject entity.
-
C.
doesNotUse
chosen
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
usesBrandColor
Indicates that one entity applies or displays another entity’s official brand color in its appearance, design, or materials.
-
E.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:16 p.m.