Triple
T1649204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 14 |
E35652
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | BCP 14 |
E35652
|
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 14 | Statement: [BCP 14, hasAbbreviation, BCP 14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 14 Context triple: [BCP 14, hasAbbreviation, BCP 14]
-
A.
BCP 14
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
RFC 3414
RFC 3414 is an Internet standard that specifies the User-based Security Model (USM) for securing SNMPv3 communications, including authentication and privacy mechanisms.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a6537e0819082b966023e0c0583 |
completed | March 5, 2026, 4:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad60a73a288190a659e2a1f09ba524 |
completed | March 8, 2026, 11:42 a.m. |
Created at: March 4, 2026, 7:29 p.m.