Triple
T5770860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6146 |
E127326
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 6147 |
E522228
|
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 6147 | Statement: [RFC 6146, relatedTo, RFC 6147]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6147 Context triple: [RFC 6146, relatedTo, RFC 6147]
-
A.
RFC 6147
chosen
RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
-
B.
RFC 4347
RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
E.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029ac21ec81908d88ba72e966d7cb |
completed | March 22, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a16ea7108190adb0756dac94c42c |
completed | March 23, 2026, 2:11 a.m. |
Created at: March 22, 2026, 3:50 p.m.