Triple

T27735328
Position Surface form Disambiguated ID Type / Status
Subject System.Net.Mail.Attachment E697514 entity
Predicate supportsContentType P640 FINISHED
Object System.Net.Mime.ContentType
System.Net.Mime.ContentType is a .NET class that represents and manipulates MIME content type headers for email and other internet media types.
E1787505 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: System.Net.Mime.ContentType | Statement: [System.Net.Mail.Attachment, supportsContentType, System.Net.Mime.ContentType]
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: System.Net.Mime.ContentType
Triple: [System.Net.Mail.Attachment, supportsContentType, System.Net.Mime.ContentType]
Generated description
System.Net.Mime.ContentType is a .NET class that represents and manipulates MIME content type headers for email and other internet media types.

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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f636a088b8819081e34d416b28cdac completed May 2, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12e4732d888190a3680cbdc50398be completed May 24, 2026, 11:43 a.m.
NEDg Description generation batch_6a12e4fd4b248190946024cf76a5bced completed May 24, 2026, 11:46 a.m.
NED2 Entity disambiguation (via description) batch_6a12e64b90cc819091f51c6cf1ecb148 completed May 24, 2026, 11:51 a.m.
Created at: April 27, 2026, 3:12 p.m.