Triple
T31593449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT |
E806161
|
entity |
| Predicate | hasHeatOfExplosion |
P191701
|
FINISHED |
| Object | about 4.2 MJ/kg (approximate) |
—
|
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: about 4.2 MJ/kg (approximate) | Statement: [TNT, hasHeatOfExplosion, about 4.2 MJ/kg (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeatOfExplosion Context triple: [TNT, hasHeatOfExplosion, about 4.2 MJ/kg (approximate)]
-
A.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
B.
explosionMechanism
Indicates the specific process or mechanism by which an explosion is initiated or occurs.
-
C.
explosiveComponents
Indicates that one entity consists of, contains, or is associated with components that are explosive or used to create an explosive device.
-
D.
explosivityIndexRange
Indicates the range of values within which an entity’s explosivity index falls.
-
E.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 30, 2026, 10:29 p.m.