Triple
T35313494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | mainDecryptionSite |
P182724
|
FINISHED |
| Object | Bletchley Park |
—
|
NE NERFINISHED |
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: Bletchley Park | Statement: [ULTRA, mainDecryptionSite, Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDecryptionSite Context triple: [ULTRA, mainDecryptionSite, Bletchley Park]
-
A.
mainDiscoverySite
Indicates the primary location where something (such as an object, specimen, or phenomenon) was originally discovered.
-
B.
deciphers
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
-
C.
decryptionCodename
Indicates that one entity serves as the codename or label used for a particular decryption operation or process involving another entity.
-
D.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
E.
decryptionRule
Indicates a rule or method used to convert encrypted data back into its original, readable form.
- F. None of above. chosen
Provenance (4 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.