Triple
T13651641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 39 |
E326753
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BCP 39 |
E326753
|
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 39 | Statement: [BCP 39, abbreviation, BCP 39]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 39 Context triple: [BCP 39, abbreviation, BCP 39]
-
A.
BCP 39
chosen
BCP 39 is an IETF Best Current Practice document that provides guidelines and recommendations for the operation and management of the Internet Engineering Steering Group (IESG).
-
B.
BIP145
BIP145 is a Bitcoin Improvement Proposal that defines support and behavior for Segregated Witness-related features in Bitcoin.
-
C.
BIP143
BIP143 is a Bitcoin Improvement Proposal that defines the new transaction digest algorithm used for signing Segregated Witness (SegWit) transactions.
-
D.
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).
-
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.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc609676c8190b5b1cabe6b315142 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78affa3c481909dba71e2ce9f44c1 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:52 p.m.