Triple

T471740
Position Surface form Disambiguated ID Type / Status
Subject Frisch–Peierls memorandum E8572 entity
Predicate proposedBombMass P7301 FINISHED
Object on the order of kilograms of uranium-235 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: on the order of kilograms of uranium-235 | Statement: [Frisch–Peierls memorandum, proposedBombMass, on the order of kilograms of uranium-235]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: proposedBombMass
Context triple: [Frisch–Peierls memorandum, proposedBombMass, on the order of kilograms of uranium-235]
  • A. bombLoad
    Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
  • B. hasAltitudeOfDetonation
    Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
  • C. explosionAltitude
    Indicates the height above a reference surface at which an explosion occurs or is triggered.
  • D. givesMassTo
    Indicates that one entity transfers or assigns a certain amount of mass to another entity.
  • E. approximateMass chosen
    Indicates that one entity has a mass value that is an estimate or close approximation of the mass 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_69a2e7f3aeb48190a19453e3a043f486 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eff0ca408190958405aec2ec6f53 completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2edecefb081908331ef8b9edf6636 completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.