Triple
T6388024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Security Coordination |
E143748
|
entity |
| Predicate | usedCoverName |
P3799
|
FINISHED |
| Object | BPCO |
E143748
|
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: BPCO | Statement: [British Security Coordination, usedCoverName, BPCO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BPCO Context triple: [British Security Coordination, usedCoverName, BPCO]
-
A.
BPCO
chosen
BPCO was a covert cover name used by the British Security Coordination, the World War II-era British intelligence and propaganda organization operating primarily in North America.
-
B.
COP
COP is the official currency code used internationally to represent the Colombian peso.
-
C.
COP
COP is the main annual United Nations climate summit where countries negotiate global agreements to address climate change.
-
D.
COP
COP is the stock ticker symbol for ConocoPhillips, a major American multinational energy company focused on oil and natural gas exploration and production.
-
E.
BHR
BHR is the three-letter ISO 3166-1 alpha-3 country code assigned to the Kingdom of Bahrain.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686b4f34819088ff07185b34e536 |
completed | March 22, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6388224fc8190aabd6e6d75887367 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:34 p.m.