Triple
T10243962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5751 |
E197861
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 3851 |
E740114
|
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 3851 | Statement: [RFC 5751, obsoletes, RFC 3851]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3851 Context triple: [RFC 5751, obsoletes, RFC 3851]
-
A.
RFC 3851
chosen
RFC 3851 is the original specification for S/MIME Version 3.1, defining how to provide cryptographic security services for MIME data such as email.
-
B.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
C.
RFC 3771
RFC 3771 is an earlier Internet Engineering Task Force (IETF) specification related to Lightweight Directory Access Protocol (LDAP) that was later superseded by RFC 4512.
-
D.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
E.
RFC 3921
RFC 3921 is an Internet standard that originally specified instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22a76188190a73df23bfb08eb3d |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7936ce4819087f07df2c7a76282 |
completed | April 9, 2026, 12:49 a.m. |
Created at: April 6, 2026, 11:26 a.m.