Triple
T17519462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Schema |
E426648
|
entity |
| Predicate | specifiedIn |
P775
|
FINISHED |
| Object | RFC 8927 |
—
|
NE NERFINISHED |
How this triple was built (3 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 8927 | Statement: [JSON Schema, specifiedIn, RFC 8927]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8927 Context triple: [JSON Schema, specifiedIn, RFC 8927]
-
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 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
-
D.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
E.
RFC 8179
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8927 Target entity description: RFC 8927 is an IETF specification that defines how to use JSON Schema for describing and validating YANG data models in network management.
-
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 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
-
D.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
E.
RFC 8179
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
- F. None of above. chosen
Provenance (2 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. |
Created at: April 10, 2026, 5:49 a.m.