Triple

T29938175
Position Surface form Disambiguated ID Type / Status
Subject GeForce 200 Series E760424 entity
Predicate includesModel P1393 FINISHED
Object GeForce GTS 250
GeForce GTS 250 is a mid-range Nvidia graphics card from the GeForce 200 series, known for offering solid performance for gaming and multimedia in its generation.
E1891156 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 GTS 250 | Statement: [GeForce 200 Series, includesModel, GeForce GTS 250]
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 GTS 250
Triple: [GeForce 200 Series, includesModel, GeForce GTS 250]
Generated description
GeForce GTS 250 is a mid-range Nvidia graphics card from the GeForce 200 series, known for offering solid performance for gaming and multimedia in its generation.

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_6a271427de5c8190988c0e25777d71a8 completed June 8, 2026, 7:12 p.m.
NEDg Description generation batch_6a27157398a88190bda7ad233606f444 completed June 8, 2026, 7:18 p.m.
NED2 Entity disambiguation (via description) batch_6a271758172c8190a7ed3f56d8d56086 completed June 8, 2026, 7:26 p.m.
Created at: April 29, 2026, 6:21 p.m.