Triple

T32771889
Position Surface form Disambiguated ID Type / Status
Subject In-Reply-To E838085 entity
Predicate instanceOf P0 FINISHED
Object email header field C58892 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: email header field
Context triple: [In-Reply-To, instanceOf, email header field]
  • A. HTTP header field
    An HTTP header field is a key-value pair in an HTTP message that conveys metadata and control information between a client and server, such as content type, caching policies, and authentication details.
  • B. general header field
    A general header field is a reusable metadata field in a message or protocol header that applies to the overall message rather than to a specific component or payload.
  • C. entity header field
    An entity header field is a metadata component in a message (such as HTTP) that describes characteristics of the message body, including its content type, length, encoding, and other entity-specific information.
  • D. protocol header field
    A protocol header field is a structured piece of metadata within a network protocol header that conveys control, addressing, or formatting information needed to correctly interpret and route the associated data.
  • E. response header field
    A response header field is a name-value pair in an HTTP response that conveys metadata about the response or the server’s handling of the request.
  • F. None of above. chosen

Provenance (1 batch)

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_69f3493a824c8190938489ba69041d08 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:13 a.m.