Triple
T10623691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5741 |
E250267
|
entity |
| Predicate | BCPNumber |
P34024
|
FINISHED |
| Object |
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.
|
E876211
|
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: BCP 78 | Statement: [RFC 5741, BCPNumber, BCP 78]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 78 Context triple: [RFC 5741, BCPNumber, BCP 78]
-
A.
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.
-
B.
BCP 9
BCP 9 is a Best Current Practice document in the IETF series that defines key procedures and guidelines for the Internet standards process.
-
C.
BCP 56
BCP 56 is a Best Current Practice document that provides guidelines and recommendations for designing and using application protocols over HTTP.
-
D.
BCP 175
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.
-
E.
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.
- 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: BCP 78 Triple: [RFC 5741, BCPNumber, BCP 78]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BCP 78 Target entity description: 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.
-
A.
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.
-
B.
BCP 9
BCP 9 is a Best Current Practice document in the IETF series that defines key procedures and guidelines for the Internet standards process.
-
C.
BCP 56
BCP 56 is a Best Current Practice document that provides guidelines and recommendations for designing and using application protocols over HTTP.
-
D.
BCP 175
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.
-
E.
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.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7f11fc8190aed858f2e1443c08 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96b9a27f881908e451bfa6c118af4 |
completed | April 10, 2026, 9:28 p.m. |
| NEDg | Description generation | batch_69d96fe942648190a8779e13e16b9196 |
completed | April 10, 2026, 9:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d970f3f78081909bcb2dae6dae06d5 |
completed | April 10, 2026, 9:51 p.m. |
Created at: April 8, 2026, 8:52 p.m.