Triple
T35299688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunny cipher |
E1019469
|
entity |
| Predicate | brokenAt |
P130694
|
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: [Tunny cipher, brokenAt, Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokenAt Context triple: [Tunny cipher, brokenAt, Bletchley Park]
-
A.
brokenOn
Indicates that an object or system ceased functioning or became damaged at a specific time or on a specific date.
-
B.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
-
C.
brokenIn
chosen
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
-
D.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
E.
brokenUsing
Indicates that one entity was broken or damaged through the use or application of another entity as the means or tool.
- 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_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.