Triple

T22027837
Position Surface form Disambiguated ID Type / Status
Subject Trickle ICE E544010 entity
Predicate definedIn P775 FINISHED
Object RFC 8839 NE NERFINISHED

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 8839 | Statement: [Trickle ICE, definedIn, RFC 8839]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 8839
Context triple: [Trickle ICE, definedIn, RFC 8839]
  • A. RFC 8439
    RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
  • B. RFC 8929
    RFC 8929 is an IETF standards document that defines the JSON Schema specification for describing and validating the structure of JSON data.
  • C. RFC 8789
    RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
  • D. RFC 8838
    RFC 8838 is an IETF specification that standardizes Trickle ICE, an extension to the ICE protocol that enables incremental, real-time gathering and exchange of connectivity candidates to speed up interactive connectivity establishment.
  • E. RFC 8729
    RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 8839
Target entity description: RFC 8839 is an IETF specification that defines the Trickle ICE mechanism for incrementally gathering and exchanging ICE candidates to speed up and improve the reliability of interactive connectivity establishment in real-time communications.
  • A. RFC 8439
    RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
  • B. RFC 8929
    RFC 8929 is an IETF standards document that defines the JSON Schema specification for describing and validating the structure of JSON data.
  • C. RFC 8789
    RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
  • D. RFC 8838 chosen
    RFC 8838 is an IETF specification that standardizes Trickle ICE, an extension to the ICE protocol that enables incremental, real-time gathering and exchange of connectivity candidates to speed up interactive connectivity establishment.
  • E. RFC 8729
    RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
  • F. None of above.

Provenance (2 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_69e11e2e8ea4819084210fe06d3a1b8d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127cdf5c08190ac804664d6e56fe2 completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:24 p.m.