Triple

T29938173
Position Surface form Disambiguated ID Type / Status
Subject GeForce 200 Series E760424 entity
Predicate includesModel P1393 FINISHED
Object GeForce GTX 285
The GeForce GTX 285 is a high-end NVIDIA graphics card from the late 2000s era, known for its strong gaming performance and use of the GT200 GPU architecture.
E1905533 NE FINISHED

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 285 | Statement: [GeForce 200 Series, includesModel, GeForce GTX 285]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: GeForce GTX 285
Triple: [GeForce 200 Series, includesModel, GeForce GTX 285]
Generated description
The GeForce GTX 285 is a high-end NVIDIA graphics card from the late 2000s era, known for its strong gaming performance and use of the GT200 GPU architecture.

Provenance (5 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_69f22463f3648190a603c3ff305c660b completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f677d7ab2c8190a26f161c559ed05b completed May 2, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a276423a10c81909ad5bd597b8e3abe completed June 9, 2026, 12:53 a.m.
NEDg Description generation batch_6a27651946d08190a4a5c4ea6dd54f73 completed June 9, 2026, 12:58 a.m.
NED2 Entity disambiguation (via description) batch_6a27661767f081909e0291186c5d6778 completed June 9, 2026, 1:02 a.m.
Created at: April 29, 2026, 6:21 p.m.