Triple
T15646037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blandford–Znajek process |
E376179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysical process |
C4776
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: astrophysical process Context triple: [Blandford–Znajek process, instanceOf, astrophysical process]
-
A.
astrophysical instability
An astrophysical instability is a physical process in which small perturbations in an astronomical system grow over time, potentially leading to dramatic structural or dynamical changes such as star formation, disk fragmentation, or explosive events.
-
B.
astrophysical model
An astrophysical model is a theoretical or computational framework that describes and predicts the physical processes, structures, and evolution of astronomical objects and phenomena in the universe.
-
C.
cosmological process
A cosmological process is a large-scale physical or dynamical phenomenon that shapes the origin, evolution, and structure of the universe over cosmic time.
-
D.
astronomical phenomenon
chosen
An astronomical phenomenon is any observable event or process that occurs in outer space or the Earth's atmosphere due to the behavior and interaction of celestial bodies and cosmic forces.
-
E.
astrophysical stability criterion
An astrophysical stability criterion is a theoretical condition or set of conditions used to determine whether an astronomical system (such as a star, disk, or gas cloud) will remain in equilibrium or undergo collapse, fragmentation, or other dynamical instabilities.
- F. None of above.
Provenance (1 batch)
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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:15 a.m.