Triple
T13297529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hut 4 |
E316723
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Hut 8 |
E310473
|
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 8 | Statement: [Hut 4, adjacentTo, Hut 8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hut 8 Context triple: [Hut 4, adjacentTo, Hut 8]
-
A.
Hut 8
chosen
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.
-
B.
Hut 6
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.
-
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 11
Hut 11 was one of the specialized wartime codebreaking huts at Bletchley Park, involved in processing and managing decrypted communications during World War II.
-
E.
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.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990a2f2708190a8f2aa7e7c0b92d2 |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7305fd57881909c1d7f09f3c084cf |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:28 p.m.