Triple
T2081550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boltzmann–Gibbs entropy |
E45253
|
entity |
| Predicate | standardFormula |
P2310
|
FINISHED |
| Object | S = -k_B \sum_i p_i \ln p_i |
—
|
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: S = -k_B \sum_i p_i \ln p_i | Statement: [Boltzmann–Gibbs entropy, standardFormula, S = -k_B \sum_i p_i \ln p_i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFormula Context triple: [Boltzmann–Gibbs entropy, standardFormula, S = -k_B \sum_i p_i \ln p_i]
-
A.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
B.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
standardComposition
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
E.
keyFormula
chosen
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
- 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_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. |
Created at: March 4, 2026, 7:41 p.m.