Triple
T10447665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7320 |
E246334
|
entity |
| Predicate | publishedAs |
P23558
|
FINISHED |
| Object | RFC 7320 |
E246334
|
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 7320 | Statement: [RFC 7320, publishedAs, RFC 7320]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7320 Context triple: [RFC 7320, publishedAs, RFC 7320]
-
A.
RFC 7320
chosen
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
B.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
C.
RFC 7432
RFC 7432 is an IETF standard that defines Ethernet VPN (EVPN), a BGP-based control plane for multipoint Layer 2 VPN services over IP/MPLS networks.
-
D.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
E.
RFC 7530
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdc10c8081908a3801fe1dea63de |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ef4e0dc81908d7cf0f2b6f4cd98 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 6, 2026, 12:16 p.m.