Triple
T21066651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye temperature |
E518989
|
entity |
| Predicate | isTypicallyHighFor |
P17855
|
FINISHED |
| Object | covalent solids |
—
|
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: covalent solids | Statement: [Debye temperature, isTypicallyHighFor, covalent solids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyHighFor Context triple: [Debye temperature, isTypicallyHighFor, covalent solids]
-
A.
hasHigh
chosen
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
C.
isHighestOfGroup
Indicates that an entity has the greatest value or rank within a specified group, with no other member exceeding it.
-
D.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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.