Triple
T9312883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2870 |
E224046
|
entity |
| Predicate | BCPNumber |
P34024
|
FINISHED |
| Object | BCP 40 |
E792106
|
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 40 | Statement: [RFC 2870, BCPNumber, BCP 40]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 40 Context triple: [RFC 2870, BCPNumber, BCP 40]
-
A.
BCP 40
chosen
BCP 40 is an IETF Best Current Practice document that defines modern requirements and guidelines for the use of IPv4 and IPv6 in the Internet.
-
B.
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.
-
C.
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.
-
D.
BCP
BCP is the commonly used abbreviation for the Bulgarian Communist Party, the former ruling communist party of Bulgaria during the socialist era.
-
E.
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.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e39d03508190aca18600c33bfdd8 |
completed | April 4, 2026, 10:10 a.m. |
Created at: March 30, 2026, 7:37 p.m.