Triple
T35299515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombe |
E1019465
|
entity |
| Predicate | producedOutput |
P66288
|
FINISHED |
| Object | candidate Enigma keys |
—
|
LITERAL 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: candidate Enigma keys | Statement: [Bombe, producedOutput, candidate Enigma keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedOutput Context triple: [Bombe, producedOutput, candidate Enigma keys]
-
A.
outputOf
chosen
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
C.
productionOutcome
Indicates the result or consequence produced by a given production process, activity, or event.
-
D.
producedVolume
Indicates the quantity or amount of something that has been produced within a specified context or period.
-
E.
producedModel
Indicates that one entity created, manufactured, or generated the other entity as a model or product.
- 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_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:03 p.m.