Triple
T12515642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EdDSA |
E299184
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 8032 |
E831075
|
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 8032 | Statement: [EdDSA, standardizedIn, RFC 8032]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8032 Context triple: [EdDSA, standardizedIn, RFC 8032]
-
A.
RFC 8032
chosen
RFC 8032 is an IETF standard that specifies the EdDSA family of high-speed, secure digital signature schemes, including Ed25519 and Ed448, for use in modern cryptographic applications.
-
B.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
C.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
D.
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
E.
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.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541f80148190976d1d912fe155d0 |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64bbd58b88190baeb99380babf64f |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.