Triple
T2081573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boltzmann–Gibbs entropy |
E45253
|
entity |
| Predicate | increasesWith |
P35660
|
FINISHED |
| Object | irreversible processes |
—
|
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: irreversible processes | Statement: [Boltzmann–Gibbs entropy, increasesWith, irreversible processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increasesWith Context triple: [Boltzmann–Gibbs entropy, increasesWith, irreversible processes]
-
A.
increases
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
B.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence or process.
-
C.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
D.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
-
E.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba35c2588190933dba882f52dd17 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.