Triple
T11244713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabi oscillation |
E266172
|
entity |
| Predicate | occursUnderCondition |
P61769
|
FINISHED |
| Object | near-resonant driving |
—
|
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: near-resonant driving | Statement: [Rabi oscillation, occursUnderCondition, near-resonant driving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursUnderCondition Context triple: [Rabi oscillation, occursUnderCondition, near-resonant driving]
-
A.
holdsUnderCondition
chosen
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
B.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
C.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
D.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
E.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e91c045c81908a9024a8aee32f4d |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.