Triple
T1631686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1157 |
E35269
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 3417 |
E38276
|
NE FINISHED |
How this triple was built (2 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 3417 | Statement: [RFC 1157, obsoletedBy, RFC 3417]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3417 Context triple: [RFC 1157, obsoletedBy, RFC 3417]
-
A.
RFC 3417
chosen
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
-
D.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f5ae98819091ce5e00eb4256a2 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad79813b2c819093bf3833db398f22 |
completed | March 8, 2026, 1:28 p.m. |
Created at: March 4, 2026, 7:28 p.m.