Triple
T33370147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 5 nuclear bomb |
E854464
|
entity |
| Predicate | usedInTestSeries |
P53947
|
FINISHED |
| Object | Operation Upshot–Knothole |
—
|
NE NERFINISHED |
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: Operation Upshot–Knothole | Statement: [Mark 5 nuclear bomb, usedInTestSeries, Operation Upshot–Knothole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTestSeries Context triple: [Mark 5 nuclear bomb, usedInTestSeries, Operation Upshot–Knothole]
-
A.
usedInSeries
chosen
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
B.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
C.
testedAs
Indicates that one entity has been evaluated, examined, or subjected to a test in the role or capacity of another specified entity or condition.
-
D.
testedInCase
Indicates that something (such as a method, component, or behavior) is exercised or verified within a particular test case.
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 1, 2026, 1:35 a.m.