Triple
T1459796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6557 |
E31484
|
entity |
| Predicate | bcpNumber |
P17884
|
FINISHED |
| Object |
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.
|
E167593
|
NE FINISHED |
How this triple was built (5 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 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.
-
B.
BCP
BCP is New York State’s Brownfield Cleanup Program, which provides incentives and a regulatory framework for the remediation and redevelopment of contaminated properties.
-
C.
BCP
BCP is the commonly used abbreviation for the Bulgarian Communist Party, the former ruling communist party of Bulgaria during the socialist era.
-
D.
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.
-
E.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related 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 175 Triple: [RFC 6557, bcpNumber, BCP 175]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BCP 175 Target entity description: 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.
-
A.
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.
-
B.
BCP
BCP is New York State’s Brownfield Cleanup Program, which provides incentives and a regulatory framework for the remediation and redevelopment of contaminated properties.
-
C.
BCP
BCP is the commonly used abbreviation for the Bulgarian Communist Party, the former ruling communist party of Bulgaria during the socialist era.
-
D.
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.
-
E.
RFC 7919
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bcpNumber Context triple: [RFC 6557, bcpNumber, BCP 175]
-
A.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
-
B.
serialNumber
chosen
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
stateBillNumber
Indicates the specific identifying number assigned to a bill within a particular state legislature.
-
E.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
- F. None of above.
Provenance (6 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e786a208190a57c4e1878c66517 |
completed | March 8, 2026, 5:51 a.m. |
| NEDg | Description generation | batch_69ad0ee93c4c8190bd705e31d9492158 |
completed | March 8, 2026, 5:53 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ad0fb331e881908455844135bb3208 |
completed | March 8, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.