Triple
T14164149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Centerboard II |
E351025
|
entity |
| Predicate | weaponYield |
P25889
|
FINISHED |
| Object | approximately 21 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 21 kilotons of TNT | Statement: [Operation Centerboard II, weaponYield, approximately 21 kilotons of TNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponYield Context triple: [Operation Centerboard II, weaponYield, approximately 21 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.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
C.
warheadMass
Indicates the mass or weight of a warhead associated with an entity or system.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.