Triple
T22028018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Session Description Protocol |
E544013
|
entity |
| Predicate | relatedSpecification |
P37
|
FINISHED |
| Object |
RFC 3264
RFC 3264 is an IETF standard that defines the offer/answer model for negotiating multimedia sessions using the Session Description Protocol (SDP).
|
E1514711
|
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 3264 | Statement: [Session Description Protocol, relatedSpecification, RFC 3264]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3264 Context triple: [Session Description Protocol, relatedSpecification, RFC 3264]
-
A.
RFC 3406
RFC 3406 is an IETF document that specifies the procedures and requirements for registering Uniform Resource Name (URN) namespaces.
-
B.
RFC 3366
RFC 3366 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines earlier PPP-related specifications to improve performance and behavior over diverse network environments.
-
C.
RFC 2764
RFC 2764 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for virtual private networks (VPNs) before being superseded by later standards.
-
D.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
E.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
- 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 3264 Triple: [Session Description Protocol, relatedSpecification, RFC 3264]
Generated description
RFC 3264 is an IETF standard that defines the offer/answer model for negotiating multimedia sessions using the Session Description Protocol (SDP).
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3264 Target entity description: RFC 3264 is an IETF standard that defines the offer/answer model for negotiating multimedia sessions using the Session Description Protocol (SDP).
-
A.
RFC 3406
RFC 3406 is an IETF document that specifies the procedures and requirements for registering Uniform Resource Name (URN) namespaces.
-
B.
RFC 3366
RFC 3366 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines earlier PPP-related specifications to improve performance and behavior over diverse network environments.
-
C.
RFC 2764
RFC 2764 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for virtual private networks (VPNs) before being superseded by later standards.
-
D.
RFC 3492
RFC 3492 is the Internet standard document that defines Punycode, an encoding method used to represent Unicode characters in domain names using only ASCII characters.
-
E.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a738ada68819098355c1953b9c3cc |
completed | May 18, 2026, 2:03 a.m. |
| NEDg | Description generation | batch_6a0a74e81da881908c73d864258dcdd5 |
completed | May 18, 2026, 2:09 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a75cbb2408190b058713432b048a2 |
completed | May 18, 2026, 2:13 a.m. |
Created at: April 16, 2026, 8:24 p.m.