Triple
T21066366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye model |
E518983
|
entity |
| Predicate | cutoffParameter |
P14326
|
FINISHED |
| Object | Debye frequency |
—
|
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: Debye frequency | Statement: [Debye model, cutoffParameter, Debye frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutoffParameter Context triple: [Debye model, cutoffParameter, Debye frequency]
-
A.
cutOff
Indicates that one entity causes another entity to be disconnected, interrupted, or severed from a source, flow, or continuation.
-
B.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
-
C.
thresholdFor
chosen
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
D.
closureThreshold
Indicates the limit or boundary value at which a process, operation, or state is considered complete or closed.
-
E.
cutOffDateYear
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
- 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:44 p.m.