Triple
T33766848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 53 nuclear bomb |
E865252
|
entity |
| Predicate | destructiveCapability |
P7134
|
FINISHED |
| Object | city-scale destruction |
—
|
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: city-scale destruction | Statement: [Mark 53 nuclear bomb, destructiveCapability, city-scale destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructiveCapability Context triple: [Mark 53 nuclear bomb, destructiveCapability, city-scale destruction]
-
A.
threatensToDestroy
Indicates that one entity has expressed an intention or warning that it will cause the complete ruin or elimination of another entity or object.
-
B.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
-
C.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
D.
weaponCapability
chosen
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.