Triple
T471738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisch–Peierls memorandum |
E8572
|
entity |
| Predicate | proposedWeaponType |
P9724
|
FINISHED |
| Object | uranium-based atomic bomb |
—
|
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: uranium-based atomic bomb | Statement: [Frisch–Peierls memorandum, proposedWeaponType, uranium-based atomic bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedWeaponType Context triple: [Frisch–Peierls memorandum, proposedWeaponType, uranium-based atomic bomb]
-
A.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
B.
weaponTypeTested
Indicates that a specific type of weapon has been subjected to a test or evaluation in the described context.
-
C.
involvesWeaponType
chosen
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
-
D.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
E.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
- 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.