Triple
T14539312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONC RPC |
E341127
|
entity |
| Predicate | previouslySpecifiedIn |
P33255
|
FINISHED |
| Object |
RFC 1831
RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
|
E1103999
|
NE FINISHED |
How this triple was built (5 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 1831 | Statement: [ONC RPC, previouslySpecifiedIn, RFC 1831]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1831 Context triple: [ONC RPC, previouslySpecifiedIn, RFC 1831]
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
-
C.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
D.
RFC 1889
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
E.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 1831 Triple: [ONC RPC, previouslySpecifiedIn, RFC 1831]
Generated description
RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1831 Target entity description: RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
-
C.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
-
D.
RFC 1889
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
E.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslySpecifiedIn Context triple: [ONC RPC, previouslySpecifiedIn, RFC 1831]
-
A.
previouslyDefinedIn
chosen
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
B.
firstSpecified
Indicates that the subject is the earliest or initial entity explicitly designated or chosen among a set of specified entities.
-
C.
previouslyRequired
Indicates that one entity was required or necessary before another entity, typically as a prerequisite condition or step.
-
D.
previouslyCovered
Indicates that the subject has already been addressed, discussed, or dealt with at an earlier time or in a prior context.
-
E.
previouslyIssued
Indicates that something was issued or released at an earlier time prior to the current reference point.
- F. None of above.
Provenance (6 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bd0dd4819094c8b2f2aa6b1c5e |
completed | April 14, 2026, 9:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a5cca788190aa8762d860c78721 |
completed | May 8, 2026, 5:53 a.m. |
| NEDg | Description generation | batch_69fd7b1452d48190b95187cc6b6e5b6a |
completed | May 8, 2026, 5:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd7b9387988190abb20ea06c04d6cc |
completed | May 8, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.