Triple
T21688716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Bomba |
E535300
|
entity |
| Predicate | designedYield |
P32569
|
FINISHED |
| Object | 100 megatons of TNT |
—
|
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: 100 megatons of TNT | Statement: [Tsar Bomba, designedYield, 100 megatons of TNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedYield Context triple: [Tsar Bomba, designedYield, 100 megatons of TNT]
-
A.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
B.
yieldPotential
chosen
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
requiresLowerMaximumYields
Indicates that one entity imposes a constraint on another such that the allowed or achievable maximum yields must be reduced.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cd51d481908df67e4f69826b06 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.