Triple
T22430048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6860 |
E554473
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 5340 |
—
|
NE NERFINISHED |
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 5340 | Statement: [RFC 6860, relatedTo, RFC 5340]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5340 Context triple: [RFC 6860, relatedTo, RFC 5340]
-
A.
RFC 5340
chosen
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 4604
RFC 4604 is an Internet Engineering Task Force (IETF) standard that specifies enhancements and clarifications for the Internet Group Management Protocol (IGMP) used in IP multicast communication.
-
D.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
E.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
Created at: April 16, 2026, 8:47 p.m.