Triple

T8611098
Position Surface form Disambiguated ID Type / Status
Subject Internet Printing Protocol E203914 entity
Predicate hasRFC P83873 FINISHED
Object RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
E745323 NE FINISHED

How this triple was built (4 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 3380 | Statement: [Internet Printing Protocol, hasRFC, RFC 3380]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 3380
Context triple: [Internet Printing Protocol, hasRFC, RFC 3380]
  • A. RFC 3008
    RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
  • B. RFC 3980
    RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
  • C. RFC 4380
    RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
  • D. RFC 3490
    RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
  • E. RFC 3090
    RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: RFC 3380
Triple: [Internet Printing Protocol, hasRFC, RFC 3380]
Generated description
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 3380
Target entity description: RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
  • A. RFC 3008
    RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
  • B. RFC 3980
    RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
  • C. RFC 4380
    RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
  • D. RFC 3490
    RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
  • E. RFC 3090
    RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
  • 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_69ca832c23e4819095a9f3eea4a21828 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc5c2d852081908901f5d2a47035b0 completed March 31, 2026, 11:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea91456a88190a7416b0f1a0327d6 completed April 2, 2026, 5:36 p.m.
NEDg Description generation batch_69cea9e685388190a4be9d2135dc02d0 completed April 2, 2026, 5:39 p.m.
NED2 Entity disambiguation (via description) batch_69ceaababe2c8190bc47430d33bfdbaa completed April 2, 2026, 5:43 p.m.
Created at: March 30, 2026, 6:25 p.m.