Triple
T33224474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 1 nuclear bomb |
E850515
|
entity |
| Predicate | fissileCoreType |
P176224
|
FINISHED |
| Object | uranium projectile and target |
—
|
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 projectile and target | Statement: [Mark 1 nuclear bomb, fissileCoreType, uranium projectile and target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fissileCoreType Context triple: [Mark 1 nuclear bomb, fissileCoreType, uranium projectile and target]
-
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.
fuelAssemblyType
Indicates the specific design or classification of a fuel assembly associated with an entity.
-
C.
nucleusType
Indicates the specific kind or classification of nucleus associated with an entity.
-
D.
hasNuclearReactorType
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
-
E.
controlRodMaterial
Indicates the material from which a control rod is made in a nuclear or control system context.
- F. None of above. chosen
Provenance (4 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_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.