Triple
T16939151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Buster–Jangle |
E410904
|
entity |
| Predicate | UncleYield |
P26004
|
FINISHED |
| Object | 1.2 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: 1.2 kilotons of TNT | Statement: [Operation Buster–Jangle, UncleYield, 1.2 kilotons of TNT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UncleYield Context triple: [Operation Buster–Jangle, UncleYield, 1.2 kilotons of TNT]
-
A.
uncle
Indicates a familial relationship where one person is the brother (or brother-in-law) of another person's parent.
-
B.
hasYield
chosen
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
C.
yieldPotential
Indicates the expected amount or capacity of output, production, or benefit that something can generate under given conditions.
-
D.
halfUncleOf
Indicates a familial relationship where one person is the half-brother of a parent of another person, making him that person's half-uncle.
-
E.
stepUncle
Indicates a relationship where a man is the (step)brother of one’s parent or the husband of one’s (step)aunt, making him a step-uncle of the other person.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2c44288190a105761ae646989e |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.