Triple
T11033177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Secure Shell (SSH) Protocol Assigned Numbers |
E260809
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 1907 |
E203677
|
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 1907 | Statement: [The Secure Shell (SSH) Protocol Assigned Numbers, obsoletes, RFC 1907]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1907 Context triple: [The Secure Shell (SSH) Protocol Assigned Numbers, obsoletes, RFC 1907]
-
A.
RFC 1907
chosen
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
B.
RFC 2197
RFC 2197 is an obsolete Internet standards document that originally defined the SMTP "ONDEMAND" extension before being superseded by RFC 2821.
-
C.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
RFC 1904
RFC 1904 is an Internet standards document that originally defined the textual conventions for SNMPv2 before later being superseded by RFC 3410.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9a6db688190a740b787448d97b2 |
completed | April 18, 2026, 3:56 p.m. |
Created at: April 8, 2026, 9:25 p.m.