Triple
T30065724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 600 Series |
E764025
|
entity |
| Predicate | includesMobileVariants |
P66849
|
FINISHED |
| Object | GeForce GTX 680M |
—
|
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 GTX 680M | Statement: [GeForce 600 Series, includesMobileVariants, GeForce GTX 680M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMobileVariants Context triple: [GeForce 600 Series, includesMobileVariants, GeForce GTX 680M]
-
A.
mobileVariant
chosen
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
B.
isMobile
Indicates that an entity is capable of moving or being moved freely rather than remaining fixed in one place.
-
C.
supportsModelVariant
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
-
D.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
E.
isMobileBase
Indicates that an entity serves as a movable or mobile base or platform for other entities or operations.
- 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_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 29, 2026, 6:59 p.m.