Triple
T10340632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umklapp scattering |
E243118
|
entity |
| Predicate | dominantAt |
P34275
|
FINISHED |
| Object | high temperatures |
—
|
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: high temperatures | Statement: [Umklapp scattering, dominantAt, high temperatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantAt Context triple: [Umklapp scattering, dominantAt, high temperatures]
-
A.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
B.
dominantDuring
chosen
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
D.
dominantUntil
Indicates that one entity maintains dominance over another up to, but not beyond, a specified point or condition in time.
-
E.
dominantInBranch
Indicates that one entity holds primary control, influence, or authority over others within a specific branch or subdivision of a larger structure or organization.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:54 a.m.