Triple
T5480293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTP |
E123450
|
entity |
| Predicate | payloadTypesDefinedIn |
P8440
|
FINISHED |
| Object |
RFC 3551
RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
|
E523057
|
NE FINISHED |
How this triple was built (5 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 3551 | Statement: [RTP, payloadTypesDefinedIn, RFC 3551]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3551 Context triple: [RTP, payloadTypesDefinedIn, RFC 3551]
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
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.
-
C.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
D.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- 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 3551 Triple: [RTP, payloadTypesDefinedIn, RFC 3551]
Generated description
RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3551 Target entity description: RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
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.
-
C.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
D.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadTypesDefinedIn Context triple: [RTP, payloadTypesDefinedIn, RFC 3551]
-
A.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
compatiblePayload
Indicates that one entity can be safely or effectively used as the payload of another entity without conflict or required modification.
-
C.
payloadCount
Indicates the number of payload items associated with or carried by a given entity or operation.
-
D.
payloadSpecialist
Indicates that an entity serves in the role of a payload specialist, responsible for managing or operating specific payloads or experiments in a mission or operation.
-
E.
publicBodyType
Indicates the classification or category of a public body (such as its organizational or legal type) within a governmental or public-sector context.
- F. None of above.
Provenance (6 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a2880c8190ad76cf8c3862aede |
completed | March 22, 2026, 1:40 a.m. |
| NEDg | Description generation | batch_69bf4a95375881909ba730ad108eee8b |
completed | March 22, 2026, 1:49 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf4afb47a88190a66de6b6c7d5c241 |
completed | March 22, 2026, 1:50 a.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.