Triple
T35299636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz cipher |
E1019468
|
entity |
| Predicate | interceptedAt |
P141297
|
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: [Lorenz cipher, interceptedAt, Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interceptedAt Context triple: [Lorenz cipher, interceptedAt, Bletchley Park]
-
A.
interceptedBy
Indicates that an action, communication, or movement is stopped, captured, or diverted by another agent before reaching its intended target or destination.
-
B.
locationOfInterception
chosen
Indicates the place where an interception event occurs between entities.
-
C.
interceptRepresents
Indicates that one entity acts as a representation or model of the interception of another entity or process.
-
D.
interceptionTimeRemaining
Indicates the amount of time left before an interception event between entities is expected to occur.
-
E.
designedToIntercept
Indicates that one entity is purposefully created or configured to detect, block, or otherwise interrupt the actions, movement, or effects of another entity.
- F. None of above.
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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.