Triple
T30863170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth’s radiation belts |
E786118
|
entity |
| Predicate | radiationSource |
P115734
|
FINISHED |
| Object | trapped solar wind particles |
—
|
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: trapped solar wind particles | Statement: [Earth’s radiation belts, radiationSource, trapped solar wind particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiationSource Context triple: [Earth’s radiation belts, radiationSource, trapped solar wind particles]
-
A.
ionizingSource
Indicates that the subject acts as a source that produces or emits ionizing radiation affecting the object.
-
B.
radiatedFrom
chosen
Indicates that something (such as energy, particles, or influence) originates at a source and spreads outward from that source.
-
C.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
D.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
E.
radiationLevel
Indicates the intensity or amount of radiation present in or emitted by an entity or environment.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691aa2ad48190b80eff3be46cdf1e |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.