Triple
T31593448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT |
E806161
|
entity |
| Predicate | hasDetonationPressure |
P196664
|
FINISHED |
| Object | on the order of 210 kbar (cast TNT) |
—
|
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: on the order of 210 kbar (cast TNT) | Statement: [TNT, hasDetonationPressure, on the order of 210 kbar (cast TNT)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetonationPressure Context triple: [TNT, hasDetonationPressure, on the order of 210 kbar (cast TNT)]
-
A.
hasDetonationVelocity
Indicates the specific speed at which a material’s detonation wave propagates through it during an explosive reaction.
-
B.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
C.
detonationCondition
Indicates the specific circumstances or triggers under which a detonation occurs or is initiated.
-
D.
detonationDepth
Indicates the depth or distance from a reference point at which a detonation occurs.
-
E.
hasHeatOfExplosion
Indicates that an entity possesses a specified amount or measure of energy released as heat during an explosive reaction.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: April 30, 2026, 10:29 p.m.