Triple
T33224473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 1 nuclear bomb |
E850515
|
entity |
| Predicate | usesFissileMaterial |
P16405
|
FINISHED |
| Object | 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: uranium-235 | Statement: [Mark 1 nuclear bomb, usesFissileMaterial, uranium-235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFissileMaterial Context triple: [Mark 1 nuclear bomb, usesFissileMaterial, uranium-235]
-
A.
fissileWith
Indicates that one material can undergo or sustain nuclear fission when interacting with another specified material or under conditions defined by that material.
-
B.
nuclearMaterial
chosen
Indicates that the subject entity is or contains nuclear material, or is directly associated with nuclear substances used for energy, research, or weapons.
-
C.
controlRodMaterial
Indicates the material from which a control rod is made in a nuclear or control system context.
-
D.
fissileCoreType
Indicates the specific type or classification of a fissile material core involved in a nuclear-related context.
-
E.
hasNuclearReactorType
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:30 a.m.