Triple
T17684159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B53 nuclear bomb |
E440845
|
entity |
| Predicate | maximumYieldClass |
P128568
|
FINISHED |
| Object | multi-megaton |
—
|
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: multi-megaton | Statement: [B53 nuclear bomb, maximumYieldClass, multi-megaton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumYieldClass Context triple: [B53 nuclear bomb, maximumYieldClass, multi-megaton]
-
A.
requiresLowerMaximumYields
Indicates that one entity imposes a constraint on another such that the allowed or achievable maximum yields must be reduced.
-
B.
identifiesMaximumWith
Indicates that one entity designates or associates another entity as having the greatest value, degree, or extent within a specified set or context.
-
C.
dominantClass
Indicates that one class or category holds primary authority, influence, or precedence over others within a given context.
-
D.
largestTestYieldLocation
Indicates the location where the subject’s largest test yield (e.g., maximum output, result, or impact from a test) occurred.
-
E.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704710488190826aaf0bdd4b2088 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.