Triple
T1631652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 855 |
E35268
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 854 |
E35267
|
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 854 | Statement: [RFC 855, relatedTo, RFC 854]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 854 Context triple: [RFC 855, relatedTo, RFC 854]
-
A.
RFC 854
chosen
RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
-
B.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
C.
RFC 3418
RFC 3418 is an Internet standard that specifies the Management Information Base (MIB) for the Simple Network Management Protocol (SNMP), defining core managed objects used for network monitoring and control.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 1905
RFC 1905 is an Internet standards document that specifies the protocol operations for the Simple Network Management Protocol version 2 (SNMPv2).
- 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_69ad58d79bc88190bfc62f53dd8e8b90 |
completed | March 8, 2026, 11:09 a.m. |
Created at: March 4, 2026, 7:28 p.m.