Triple
T1449134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urakami district of Nagasaki |
E31247
|
entity |
| Predicate | bombUsed |
P21566
|
FINISHED |
| Object | plutonium implosion-type 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: plutonium implosion-type atomic bomb | Statement: [Urakami district of Nagasaki, bombUsed, plutonium implosion-type atomic bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombUsed Context triple: [Urakami district of Nagasaki, bombUsed, plutonium implosion-type atomic bomb]
-
A.
bombLoad
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
-
B.
bombingMethod
Indicates the method or technique used to carry out a bombing.
-
C.
bombTonnageDropped
Indicates the total weight of bombs that were released or deployed in a given event or context.
-
D.
explosiveDevice
chosen
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
E.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55c408c8190917ed44d9070a2fb |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.