Triple
T28051065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloch oscillations |
E708820
|
entity |
| Predicate | frequencySymbol |
P75751
|
FINISHED |
| Object | ω_B |
—
|
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: ω_B | Statement: [Bloch oscillations, frequencySymbol, ω_B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencySymbol Context triple: [Bloch oscillations, frequencySymbol, ω_B]
-
A.
symbolForFrequency
chosen
Indicates that one entity serves as the symbolic representation or notation used to denote the frequency of another entity or phenomenon.
-
B.
frequencyGivenBy
Indicates that the frequency of something is specified, determined, or provided by a particular source or entity.
-
C.
frequencyClass
Indicates how often an event, action, or relation occurs, typically by assigning it to a predefined frequency category or class.
-
D.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
E.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
- 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_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_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:33 p.m.