Triple
T33515747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Danube |
E858360
|
entity |
| Predicate | nuclearYield |
P25889
|
FINISHED |
| Object | approximately 10–12 kilotons 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: approximately 10–12 kilotons of TNT | Statement: [Blue Danube, nuclearYield, approximately 10–12 kilotons of TNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearYield Context triple: [Blue Danube, nuclearYield, approximately 10–12 kilotons of TNT]
-
A.
explosiveYieldApprox
chosen
Indicates that one entity has an approximate explosive yield value, typically expressing the estimated magnitude of an explosion or explosive device.
-
B.
nuclearTestYieldLimit
Indicates a restriction or maximum allowable explosive yield for a nuclear test.
-
C.
nuclearExplosiveType
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
D.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
E.
bombTonnageDropped
Indicates the total weight of bombs that were released or deployed in a given event or context.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.