Triple
T17519464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Schema |
E426648
|
entity |
| Predicate | specifiedIn |
P775
|
FINISHED |
| Object |
RFC 8929
RFC 8929 is an IETF standards document that defines the JSON Schema specification for describing and validating the structure of JSON data.
|
E1276849
|
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 8929 | Statement: [JSON Schema, specifiedIn, RFC 8929]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8929 Context triple: [JSON Schema, specifiedIn, RFC 8929]
-
A.
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.
-
B.
RFC 8789
RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
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 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
- 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 8929 Triple: [JSON Schema, specifiedIn, RFC 8929]
Generated description
RFC 8929 is an IETF standards document that defines the JSON Schema specification for describing and validating the structure of JSON data.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8929 Target entity description: RFC 8929 is an IETF standards document that defines the JSON Schema specification for describing and validating the structure of JSON data.
-
A.
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.
-
B.
RFC 8789
RFC 8789 is an Internet Engineering Task Force (IETF) standards-track document that updates and refines the Internet Standards Process originally defined in RFC 2026.
-
C.
RFC 8996
RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
-
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 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
- 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_6a01dddcb3148190b769e01a159fd5e7 |
completed | May 11, 2026, 1:47 p.m. |
| NEDg | Description generation | batch_6a01dfaf934481908753eb760115074a |
completed | May 11, 2026, 1:54 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01e02a5d9481909cd957c14a4eff3b |
completed | May 11, 2026, 1:56 p.m. |
Created at: April 10, 2026, 5:49 a.m.