Triple
T30065685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 600 Series |
E764025
|
entity |
| Predicate | productLineSuccessor |
P146468
|
FINISHED |
| Object | GeForce 700 Series |
—
|
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 700 Series | Statement: [GeForce 600 Series, productLineSuccessor, GeForce 700 Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLineSuccessor Context triple: [GeForce 600 Series, productLineSuccessor, GeForce 700 Series]
-
A.
successorOrRelatedProduct
chosen
Indicates that one product is a successor to, replacement for, or closely related evolution of another product.
-
B.
belongsToProductLine
Indicates that an item or product is associated with and classified under a specific product line.
-
C.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
D.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
-
E.
laterProductType
Indicates that one product type occurs or is introduced after another product type in time or sequence.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 29, 2026, 6:59 p.m.