Triple
T2924627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bletchley Park |
E78812
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Hut 6 |
E312515
|
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: Hut 6 | Statement: [Bletchley Park, hasPart, Hut 6]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hut 6 Context triple: [Bletchley Park, hasPart, Hut 6]
-
A.
Hut 6
chosen
Hut 6 was a key wartime building at Bletchley Park where British codebreakers decrypted German Army and Air Force Enigma communications during World War II.
-
B.
Hut 8
Hut 8 was a section at Bletchley Park during World War II where British codebreakers, including Alan Turing, worked on decrypting German naval Enigma communications.
-
C.
Hut 4
Hut 4 was a building at Bletchley Park that housed part of the British World War II codebreaking operations, particularly focused on naval intelligence.
-
D.
Hut 3
Hut 3 was a key wartime building at Bletchley Park where British codebreakers translated and analyzed decrypted enemy communications during World War II.
-
E.
Gunter Annex
Gunter Annex is a U.S. Air Force installation in Montgomery, Alabama, that serves as a key site for cyber, education, and support operations within the Air Force.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97c086888190ba51ce659a6c4f50 |
completed | March 8, 2026, 3:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12e181898819087ed4acfd24c00a1 |
completed | March 11, 2026, 8:55 a.m. |
Created at: March 8, 2026, 2:55 p.m.