Triple

T270880
Position Surface form Disambiguated ID Type / Status
Subject RFC 9111 E5629 entity
Predicate obsoletes P101 FINISHED
Object RFC 7234 E5629 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 7234 | Statement: [RFC 9111, obsoletes, RFC 7234]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 7234
Context triple: [RFC 9111, obsoletes, RFC 7234]
  • A. RFC 9112
    RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
  • B. RFC 9114
    RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
  • C. RFC 6557
    RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
  • D. RFC 9113
    RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
  • E. RFC 9111 chosen
    RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
  • 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: obsoletes
Context triple: [RFC 9111, obsoletes, RFC 7234]
  • A. wasSupersededBy chosen
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • B. usedInsteadOf
    Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
  • C. repealed
    Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
  • D. releaseOf
    Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
  • E. overrides
    Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
  • F. None of above.

Provenance (4 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_69a25853594c8190b05ec3a586ec88bf completed Feb. 28, 2026, 2:52 a.m.
NER Named-entity recognition batch_69a25e69a9248190b9e7959b43223baa completed Feb. 28, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69a38f51aeac81908c6d398e650dc315 completed March 1, 2026, 12:58 a.m.
PD Predicate disambiguation batch_69a25b721180819080d43c43fcbccf87 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:57 a.m.