Triple
T8113451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4035 |
E189410
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 4034 |
E195588
|
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 4034 | Statement: [RFC 4035, relatedTo, RFC 4034]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4034 Context triple: [RFC 4035, relatedTo, RFC 4034]
-
A.
RFC 4034
chosen
RFC 4034 is an Internet standards document that specifies the DNS Security Extensions (DNSSEC) resource records and their formats used to provide authentication and integrity for DNS data.
-
B.
RFC 4035
RFC 4035 is an Internet standard that specifies the protocol modifications and operational considerations for deploying DNS Security Extensions (DNSSEC) in the Domain Name System.
-
C.
RFC 5034
RFC 5034 is an Internet standard that extends the Post Office Protocol version 3 (POP3) to support Simple Authentication and Security Layer (SASL) mechanisms for enhanced email authentication and security.
-
D.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb432d7dfc8190b9c980f32c7b4623 |
completed | March 31, 2026, 3:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbea5d39c819099d52545410ae564 |
completed | April 1, 2026, 6:43 a.m. |
Created at: March 30, 2026, 5:32 p.m.