Triple
T8009157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4033 |
E186439
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 4035 |
E189410
|
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 4035 | Statement: [RFC 4033, relatedTo, RFC 4035]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4035 Context triple: [RFC 4033, relatedTo, RFC 4035]
-
A.
RFC 4035
chosen
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.
-
B.
RFC 4034
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.
-
C.
RFC 4033
RFC 4033 is an Internet standard that specifies the security extensions for the Domain Name System (DNSSEC), defining mechanisms for authenticating DNS data.
-
D.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
-
E.
RFC 4175
RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6f76408190a1312369521a187a |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63c1f76881909ad6d7777090f2e2 |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:19 p.m.