Triple
T2724426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 793 |
E60156
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1122 |
E64273
|
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 1122 | Statement: [RFC 793, relatedTo, RFC 1122]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1122 Context triple: [RFC 793, relatedTo, RFC 1122]
-
A.
RFC 1122
chosen
RFC 1122 is an Internet standard that defines host-level requirements and core behaviors for Internet protocol implementations, including TCP/IP.
-
B.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
-
C.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
D.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdacc0a6881909b64a4d22e1d7690 |
completed | March 7, 2026, 7:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb69605308190b5a8078b275791fb |
completed | March 10, 2026, 6:13 a.m. |
Created at: March 6, 2026, 9:55 p.m.