Triple
T17519465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Schema |
E426648
|
entity |
| Predicate | specifiedIn |
P775
|
FINISHED |
| Object |
RFC 8930
RFC 8930 is an IETF document that standardizes the use of JSON Schema for describing and validating JSON-based data structures in Internet protocols and applications.
|
E1274299
|
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 8930 | Statement: [JSON Schema, specifiedIn, RFC 8930]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8930 Context triple: [JSON Schema, specifiedIn, RFC 8930]
-
A.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
B.
RFC 7530
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
-
C.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
D.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
E.
RFC 9082
RFC 9082 is an IETF standard that specifies the HTTP-based query format and response structure for the Registration Data Access Protocol (RDAP), used to access domain name and Internet number registration data.
- 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 8930 Triple: [JSON Schema, specifiedIn, RFC 8930]
Generated description
RFC 8930 is an IETF document that standardizes the use of JSON Schema for describing and validating JSON-based data structures in Internet protocols and applications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8930 Target entity description: RFC 8930 is an IETF document that standardizes the use of JSON Schema for describing and validating JSON-based data structures in Internet protocols and applications.
-
A.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
B.
RFC 7530
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
-
C.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
-
D.
RFC 8439
RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
-
E.
RFC 9082
RFC 9082 is an IETF standard that specifies the HTTP-based query format and response structure for the Registration Data Access Protocol (RDAP), used to access domain name and Internet number registration data.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01c94237d08190bb1f874735c87803 |
completed | May 11, 2026, 12:19 p.m. |
| NEDg | Description generation | batch_6a01cabea2b48190a690b17a88d45b40 |
completed | May 11, 2026, 12:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01cefa08f8819086cb86ce22193baa |
completed | May 11, 2026, 12:43 p.m. |
Created at: April 10, 2026, 5:49 a.m.