Triple
T21066646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye temperature |
E518989
|
entity |
| Predicate | lowTemperatureLimitImplies |
P17139
|
FINISHED |
| Object | heat capacity proportional to T^3 |
—
|
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: heat capacity proportional to T^3 | Statement: [Debye temperature, lowTemperatureLimitImplies, heat capacity proportional to T^3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowTemperatureLimitImplies Context triple: [Debye temperature, lowTemperatureLimitImplies, heat capacity proportional to T^3]
-
A.
hasMinTemperature
Indicates that something possesses or is associated with a specified minimum temperature value.
-
B.
lowerLimit
chosen
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
C.
minimumWinterTemperature
Indicates the lowest temperature typically experienced during the winter season for the subject entity.
-
D.
lowEnergyLimit
Indicates a relationship where an entity is constrained by or subject to a minimum allowable energy level or threshold.
-
E.
isColderThan
Indicates that one entity has a lower temperature than 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb455fc81909cc63fa0e87b6a35 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:45 p.m.