Triple
T271054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best Current Practice |
E5632
|
entity |
| Predicate | hasExample |
P1259
|
FINISHED |
| Object |
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
|
E35652
|
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 14 | Statement: [Best Current Practice, hasExample, BCP 14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 14 Context triple: [Best Current Practice, hasExample, BCP 14]
-
A.
BCP 38
BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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 14 Triple: [Best Current Practice, hasExample, BCP 14]
Generated description
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BCP 14 Target entity description: BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
A.
BCP 38
BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
-
B.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
C.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db17e8c8190a6ebcadd8a0abf4d |
completed | Feb. 28, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3914eba9081908cdef8b719c9b20b |
completed | March 1, 2026, 1:07 a.m. |
| NEDg | Description generation | batch_69a391888bbc81908d86e3a1f15cb84e |
completed | March 1, 2026, 1:08 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a3921fc8c8819084d2dab21012e53a |
completed | March 1, 2026, 1:10 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.