Triple
T1814058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3410 |
E40395
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 1903 |
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 1903 | Statement: [RFC 3410, obsoletes, RFC 1903]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1903 Context triple: [RFC 3410, obsoletes, RFC 1903]
-
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 1901
RFC 1901 is an IETF standards document that specifies the community-based version of the Simple Network Management Protocol, commonly known as SNMPv2c.
-
C.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
D.
RFC 3411
RFC 3411 is an IETF standard that specifies the architecture for the Simple Network Management Protocol (SNMP) framework used for managing devices on IP networks.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa65c905ec8190bea7cd72d218487a |
completed | March 6, 2026, 5:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf42de6081908182cd3bda9c69e9 |
completed | March 8, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:32 p.m.