Triple
T34984267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-bomb |
E1008897
|
entity |
| Predicate | hasTypicalYieldHigherThan |
P13790
|
FINISHED |
| Object | fission 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: fission bomb | Statement: [H-bomb, hasTypicalYieldHigherThan, fission bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalYieldHigherThan Context triple: [H-bomb, hasTypicalYieldHigherThan, fission bomb]
-
A.
requiresLowerMaximumYields
Indicates that one entity imposes a constraint on another such that the allowed or achievable maximum yields must be reduced.
-
B.
relativeYieldComparedToW76
Indicates the yield of something expressed in comparison to the yield of the reference item W76, typically as a ratio or relative measure.
-
C.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
D.
isHigherThan
chosen
Indicates that one entity has a greater value, level, or position than another entity.
-
E.
hasHigherVariety
Indicates that one entity offers or contains a greater diversity or range of items, types, or options than 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:01 p.m.