Triple
T4091786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landauer's principle |
E87719
|
entity |
| Predicate | minimumEntropyIncreasePerBit |
P26954
|
FINISHED |
| Object | k ln 2 |
—
|
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: k ln 2 | Statement: [Landauer's principle, minimumEntropyIncreasePerBit, k ln 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumEntropyIncreasePerBit Context triple: [Landauer's principle, minimumEntropyIncreasePerBit, k ln 2]
-
A.
hasEntropy
Indicates that an entity possesses or is characterized by a certain amount or state of entropy, typically reflecting its degree of disorder or uncertainty.
-
B.
compressionRatio
Indicates the proportional reduction in size or volume achieved when something is compressed compared to its original size.
-
C.
minimumNumber
chosen
Indicates that the associated value is the smallest or least quantity allowed, required, or observed within a given set or context.
-
D.
IVLength
Indicates the measured length of an intravenous (IV) line or catheter used in a medical context.
-
E.
minimizedBy
Indicates that one entity serves to reduce, lessen, or make as small as possible the value, effect, or impact of another entity.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.