Triple

T31593910
Position Surface form Disambiguated ID Type / Status
Subject Highball E806170 entity
Predicate inspiredBy P9 FINISHED
Object dams-busting Upkeep bomb
The dams-busting Upkeep bomb was a British World War II "bouncing bomb" designed by Barnes Wallis to breach German dams during Operation Chastise in 1943.
E1968942 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: dams-busting Upkeep bomb | Statement: [Highball, inspiredBy, dams-busting Upkeep bomb]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: dams-busting Upkeep bomb
Triple: [Highball, inspiredBy, dams-busting Upkeep bomb]
Generated description
The dams-busting Upkeep bomb was a British World War II "bouncing bomb" designed by Barnes Wallis to breach German dams during Operation Chastise in 1943.

Provenance (5 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_69f348d4891c8190b02bae3c8ecb68b7 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a8332a008190949520bac1f9a0b0 completed May 3, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b56550d70819088b6012b38610d67 completed June 12, 2026, 12:44 a.m.
NEDg Description generation batch_6a2b589839208190b8adc674ec46a413 completed June 12, 2026, 12:53 a.m.
NED2 Entity disambiguation (via description) batch_6a2b5ab9e418819084b93205bc7bb374 completed June 12, 2026, 1:02 a.m.
Created at: April 30, 2026, 10:29 p.m.