Triple
T1945474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2110 |
E42046
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object |
RFC 4175
RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP networks.
|
E220604
|
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 4175 | Statement: [SMPTE ST 2110, relatedStandard, RFC 4175]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4175 Context triple: [SMPTE ST 2110, relatedStandard, RFC 4175]
-
A.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
B.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
C.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- 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 4175 Triple: [SMPTE ST 2110, relatedStandard, RFC 4175]
Generated description
RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4175 Target entity description: RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP networks.
-
A.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
B.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
C.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb300af2481908ae359972843c1ef |
completed | March 7, 2026, 5:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfbbcc5688190aad081dc8d119e7f |
completed | March 8, 2026, 10:44 p.m. |
| NEDg | Description generation | batch_69adfc50a3488190afe44ee5125d9ebd |
completed | March 8, 2026, 10:46 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adfcdccce48190a2591b90c81ad084 |
completed | March 8, 2026, 10:49 p.m. |
Created at: March 4, 2026, 7:36 p.m.