Triple
T7928285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetNext |
E184122
|
entity |
| Predicate | specifiedIn |
P775
|
FINISHED |
| Object | RFC 1157 |
E35269
|
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 1157 | Statement: [GetNext, specifiedIn, RFC 1157]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1157 Context triple: [GetNext, specifiedIn, RFC 1157]
-
A.
RFC 1157
chosen
RFC 1157 is the Internet standard document that specifies the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
B.
RFC 1457
RFC 1457 is an early Internet standards document that specified guidelines and mechanisms related to network management within the SNMP framework before being superseded by later updates.
-
C.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
D.
RFC 1907
RFC 1907 is an earlier Internet standard that defined the Management Information Base (MIB) for SNMPv2, later superseded by RFC 3418.
-
E.
RFC 1055
RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5bfd08e88190bc6b2d77a148ae57 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:07 p.m.