Triple
T3917971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian Communist Party |
E88889
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BCP |
E88889
|
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 | Statement: [Bulgarian Communist Party, abbreviation, BCP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP Context triple: [Bulgarian Communist Party, abbreviation, BCP]
-
A.
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.
-
B.
BCP
chosen
BCP is the commonly used abbreviation for the Bulgarian Communist Party, the former ruling communist party of Bulgaria during the socialist era.
-
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.
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.
-
E.
BPPC
BPPC (Basic Patient Privacy Consents) is an IHE IT Infrastructure profile that defines how healthcare systems capture, manage, and enforce patients’ privacy consent directives in electronic health information exchange.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeed5797508190adaddb84575d9bb3 |
completed | March 9, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b52864e0488190ab348a52cb9168b9 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:22 p.m.