Triple
T12209369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Bravo |
E290915
|
entity |
| Predicate | yieldErrorFactor |
P73079
|
FINISHED |
| Object | about three times predicted yield |
—
|
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: about three times predicted yield | Statement: [Castle Bravo, yieldErrorFactor, about three times predicted yield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yieldErrorFactor Context triple: [Castle Bravo, yieldErrorFactor, about three times predicted yield]
-
A.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
errorTerm
chosen
Indicates the specific discrepancy or residual value that quantifies the difference between an observed outcome and its predicted or true value in a model or calculation.
-
C.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
D.
lossType
Indicates the specific category or nature of a loss associated with an entity or event.
-
E.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.