Triple
T380059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi surface |
E8657
|
entity |
| Predicate | givesRiseTo |
P4501
|
FINISHED |
| Object | Umklapp scattering conditions |
—
|
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: Umklapp scattering conditions | Statement: [Fermi surface, givesRiseTo, Umklapp scattering conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesRiseTo Context triple: [Fermi surface, givesRiseTo, Umklapp scattering conditions]
-
A.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
B.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
C.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
D.
underlies
chosen
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
E.
developedFrom
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.