Triple
T2114329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XMPP |
E42571
|
entity |
| Predicate | hasCoreSpecification |
P5374
|
FINISHED |
| Object |
RFC 6120
RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
|
E233818
|
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 6120 | Statement: [XMPP, hasCoreSpecification, RFC 6120]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6120 Context triple: [XMPP, hasCoreSpecification, RFC 6120]
-
A.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
B.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 6020
RFC 6020 is the IETF specification that defines the YANG data modeling language used for network configuration and management protocols such as NETCONF.
-
E.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
- 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 6120 Triple: [XMPP, hasCoreSpecification, RFC 6120]
Generated description
RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6120 Target entity description: RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
-
A.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
B.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 6020
RFC 6020 is the IETF specification that defines the YANG data modeling language used for network configuration and management protocols such as NETCONF.
-
E.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreSpecification Context triple: [XMPP, hasCoreSpecification, RFC 6120]
-
A.
hasSpecification
chosen
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
C.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
E.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae3076afec819091183e328cff58c8 |
completed | March 9, 2026, 2:29 a.m. |
| NEDg | Description generation | batch_69ae30e1c7488190acd6d29c5ad10c33 |
completed | March 9, 2026, 2:30 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae316398488190b9dd38145d5488b4 |
completed | March 9, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.