Triple
T16465670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6557 |
E399925
|
entity |
| Predicate | bcpNumber |
P17884
|
FINISHED |
| Object | BCP 175 |
E167593
|
NE FINISHED |
How this triple was built (2 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: BCP 175 | Statement: [RFC 6557, bcpNumber, BCP 175]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 175 Context triple: [RFC 6557, bcpNumber, BCP 175]
-
A.
BCP 175
chosen
BCP 175 is an IETF Best Current Practice document that defines procedures and policies for managing the DNS root zone’s trust anchor for DNSSEC.
-
B.
BCP 195
BCP 195 is an IETF Best Current Practice document that provides modern security recommendations for the use of Transport Layer Security (TLS) and Datagram TLS (DTLS) in Internet protocols.
-
C.
BCP 190
BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
-
D.
BCP 57
BCP 57 is a Best Current Practice document from the IETF that provides updated guidance and recommendations related to the subject matter previously covered by RFC 1908.
-
E.
BCP 78
BCP 78 is an IETF Best Current Practice document that defines the rights, licenses, and legal framework governing contributions to IETF standards and related documents.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d841f348190958a25f35034edff |
completed | April 18, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00581a11e881908681f68c26ee6a05 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:11 a.m.