Triple
T10316161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3980 |
E242019
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFC3980 |
E242019
|
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: RFC3980 | Statement: [RFC 3980, hasAbbreviation, RFC3980]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC3980 Context triple: [RFC 3980, hasAbbreviation, RFC3980]
-
A.
RFC 3980
chosen
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
B.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
C.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
D.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
E.
RFC 3920
RFC 3920 is the original specification that defined the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP) before being superseded by RFC 6120.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d35c39148190ab2622a2204aca3b |
completed | April 7, 2026, 9:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71d86c7e481908a0d5e65f66ab2c0 |
completed | April 9, 2026, 3:31 a.m. |
Created at: April 6, 2026, 11:49 a.m.