Triple
T35299514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombe |
E1019465
|
entity |
| Predicate | requiredInput |
P199643
|
FINISHED |
| Object | cribs (known plaintext guesses) |
—
|
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: cribs (known plaintext guesses) | Statement: [Bombe, requiredInput, cribs (known plaintext guesses)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredInput Context triple: [Bombe, requiredInput, cribs (known plaintext guesses)]
-
A.
requiredIn
chosen
Indicates that one entity must be present, included, or satisfied within another entity or context as a necessary condition.
-
B.
requiredOn
Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to 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_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 3, 2026, 4:03 p.m.