Triple
T9526105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bouncing bomb |
E229763
|
entity |
| Predicate | detonationCondition |
P88555
|
FINISHED |
| Object | set depth below water surface |
—
|
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: set depth below water surface | Statement: [bouncing bomb, detonationCondition, set depth below water surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detonationCondition Context triple: [bouncing bomb, detonationCondition, set depth below water surface]
-
A.
detonationMode
Indicates the specific manner or mechanism by which a detonation is initiated or carried out in relation to an explosive event.
-
B.
detonationMethod
Indicates the method or mechanism by which an explosive device is triggered or detonated.
-
C.
detonationDepth
Indicates the depth or distance from a reference point at which a detonation occurs.
-
D.
detonationPosition
Indicates the specific location or coordinates at which a detonation occurs or is intended to occur.
-
E.
timeOfDetonation
Indicates the specific point in time at which a detonation event occurs.
- F. None of above. chosen
Provenance (4 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd989b529c81909ee18dd3d468c816 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:59 p.m.