Triple
T15614168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composition H6 |
E375369
|
entity |
| Predicate | hasDetonationVelocity |
P119433
|
FINISHED |
| Object | approximately 7,000–8,000 m/s |
—
|
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: approximately 7,000–8,000 m/s | Statement: [Composition H6, hasDetonationVelocity, approximately 7,000–8,000 m/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetonationVelocity Context triple: [Composition H6, hasDetonationVelocity, approximately 7,000–8,000 m/s]
-
A.
detonationMethod
Indicates the method or mechanism by which an explosive device is triggered or detonated.
-
B.
detonationDepth
Indicates the depth or distance from a reference point at which a detonation occurs.
-
C.
detonationMode
Indicates the specific manner or mechanism by which a detonation is initiated or carried out in relation to an explosive event.
-
D.
detonationCondition
Indicates the specific circumstances or triggers under which a detonation occurs or is initiated.
-
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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.