Triple
T14395911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CardDAV |
E356947
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 6352
RFC 6352 is the Internet standards document that specifies the CardDAV protocol for remote access and management of contact data stored on a server.
|
E1096590
|
NE FINISHED |
How this triple was built (4 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 6352 | Statement: [CardDAV, definedInRFC, RFC 6352]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6352 Context triple: [CardDAV, definedInRFC, RFC 6352]
-
A.
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.
-
B.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
-
C.
RFC 6122
RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
-
D.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
E.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
- 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 6352 Triple: [CardDAV, definedInRFC, RFC 6352]
Generated description
RFC 6352 is the Internet standards document that specifies the CardDAV protocol for remote access and management of contact data stored on a server.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6352 Target entity description: RFC 6352 is the Internet standards document that specifies the CardDAV protocol for remote access and management of contact data stored on a server.
-
A.
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.
-
B.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
-
C.
RFC 6122
RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
-
D.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
-
E.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
- F. None of above. chosen
Provenance (5 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90826f908190b3969af9b7cf922f |
completed | April 14, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd551cbdb08190a9ea53e607f2555b |
completed | May 8, 2026, 3:14 a.m. |
| NEDg | Description generation | batch_69fd55d90ed08190b6a0184715f39ff4 |
completed | May 8, 2026, 3:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd565d32fc8190acc1e733537a23cb |
completed | May 8, 2026, 3:19 a.m. |
Created at: April 10, 2026, 1:17 a.m.