Triple
T28051064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloch oscillations |
E708820
|
entity |
| Predicate | frequencyGivenBy |
P163427
|
FINISHED |
| Object | eEa/hbar |
—
|
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: eEa/hbar | Statement: [Bloch oscillations, frequencyGivenBy, eEa/hbar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyGivenBy Context triple: [Bloch oscillations, frequencyGivenBy, eEa/hbar]
-
A.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
-
B.
frequencyClass
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
C.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
frequencyContent
Indicates that one entity specifies or characterizes the rate or frequency with which the content or occurrence of another entity takes place.
-
E.
frequencyDependsOn
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
- F. None of above. chosen
Provenance (4 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd945f08190b2526b01686a1562 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f637cad530819086cad3a5ec156013 |
completed | May 2, 2026, 5:43 p.m. |
Created at: April 27, 2026, 8:33 p.m.