Triple
T10329102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA media type registry |
E242832
|
entity |
| Predicate | documentedIn |
P309
|
FINISHED |
| Object |
RFC 4288
RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
|
E856203
|
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 4288 | Statement: [IANA media type registry, documentedIn, RFC 4288]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4288 Context triple: [IANA media type registry, documentedIn, RFC 4288]
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
C.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
D.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
E.
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).
- 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 4288 Triple: [IANA media type registry, documentedIn, RFC 4288]
Generated description
RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4288 Target entity description: RFC 4288 is an Internet standards document that defines the procedures and guidelines for registering and managing media (MIME) types with IANA.
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
C.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
D.
RFC 2481
RFC 2481 is an early experimental specification that introduced Explicit Congestion Notification (ECN) for IP and TCP to signal network congestion without packet loss.
-
E.
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).
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71db4a8dc81909adb2a044e74fd6b |
completed | April 9, 2026, 3:32 a.m. |
| NEDg | Description generation | batch_69d73189d7cc8190b81bb30994b3900f |
completed | April 9, 2026, 4:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d7329891688190b5c1ec5906728f01 |
completed | April 9, 2026, 5:01 a.m. |
Created at: April 6, 2026, 11:52 a.m.