Triple

T12206536
Position Surface form Disambiguated ID Type / Status
Subject Accept-Charset E290850 entity
Predicate relatedToSpecification P103780 FINISHED
Object RFC 7231 E40362 NE FINISHED

How this triple was built (3 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: RFC 7231 | Statement: [Accept-Charset, relatedToSpecification, RFC 7231]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 7231
Context triple: [Accept-Charset, relatedToSpecification, RFC 7231]
  • A. RFC 7231 chosen
    RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
  • B. RFC 7232
    RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
  • C. RFC 7230
    RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
  • D. RFC 7234
    RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
  • E. RFC 7235
    RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: relatedToSpecification
Context triple: [Accept-Charset, relatedToSpecification, RFC 7231]
  • A. relatedTo
    Indicates a general, non-specific relationship or association exists between two entities.
  • B. relatedToProduct
    Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
  • C. relatedType
    Indicates that one entity is connected to another through a specified type or category of relationship.
  • D. relatedRequirement
    Indicates that one requirement has a defined relationship or dependency with another requirement.
  • E. relatedRule
    Indicates that one rule is connected or associated with another rule, typically through some logical, structural, or referential relationship.
  • F. None of above. chosen

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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d920e312708190b4aede2e21f5f697 completed April 10, 2026, 4:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69f61e5666f48190a28eed761e7b9210 completed May 2, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69d91c3d669c81908eea7ad61122d275 completed April 10, 2026, 3:50 p.m.
PDg Predicate description generation batch_69d920c3dc9881908c396a4ab34f4836 completed April 10, 2026, 4:09 p.m.
Created at: April 8, 2026, 9:51 p.m.