Triple
T3075823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie (Operation Crossroads) |
E64133
|
entity |
| Predicate | plannedDetonationType |
P36944
|
FINISHED |
| Object | underwater nuclear detonation |
—
|
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: underwater nuclear detonation | Statement: [Charlie (Operation Crossroads), plannedDetonationType, underwater nuclear detonation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedDetonationType Context triple: [Charlie (Operation Crossroads), plannedDetonationType, underwater nuclear detonation]
-
A.
detonationMethod
Indicates the method or mechanism by which an explosive device is triggered or detonated.
-
B.
detonationMode
chosen
Indicates the specific manner or mechanism by which a detonation is initiated or carried out in relation to an explosive event.
-
C.
timeOfDetonation
Indicates the specific point in time at which a detonation event occurs.
-
D.
detonatedBy
Indicates that an explosive or device is set off or caused to explode by a particular agent or entity.
-
E.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada150d8e08190bde5f68e800e8feb |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:02 p.m.