Triple
T21066648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye temperature |
E518989
|
entity |
| Predicate | variesBetweenMaterials |
P126080
|
FINISHED |
| Object | metals |
—
|
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: metals | Statement: [Debye temperature, variesBetweenMaterials, metals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variesBetweenMaterials Context triple: [Debye temperature, variesBetweenMaterials, metals]
-
A.
attributeVariesBy
chosen
Indicates that a particular attribute can take on different values depending on another variable, context, or condition.
-
B.
compositionVariesBy
Indicates that the composition of something differs depending on a specified factor, condition, or context.
-
C.
isMaterialSpecific
Indicates that a relationship, rule, or property applies only to a particular material or set of materials, rather than being generally applicable.
-
D.
basedOnMaterialBy
Indicates that something is derived, adapted, or developed from source material created by a specified entity.
-
E.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
- 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.