Triple
T2920037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Stoff |
E78696
|
entity |
| Predicate | decompositionProduct |
P42358
|
FINISHED |
| Object | steam |
—
|
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: steam | Statement: [T-Stoff, decompositionProduct, steam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decompositionProduct Context triple: [T-Stoff, decompositionProduct, steam]
-
A.
yieldsDecomposition
chosen
Indicates that one entity produces or results in a particular breakdown or decomposition of another entity.
-
B.
numericDecomposition
Indicates that a number is broken down into a set of component numbers or factors whose combination (e.g., sum or product) reconstructs the original value.
-
C.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
D.
canBeDissolvedWith
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
E.
isMetabolizedBy
Indicates that a substance is biochemically broken down or transformed through metabolic processes carried out by a specified organism, cell type, or enzyme system.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.