Triple
T22175237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Lights |
E548031
|
entity |
| Predicate | oftenTriggeredBy |
P96153
|
FINISHED |
| Object | coronal mass ejections |
—
|
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: coronal mass ejections | Statement: [Northern Lights, oftenTriggeredBy, coronal mass ejections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenTriggeredBy Context triple: [Northern Lights, oftenTriggeredBy, coronal mass ejections]
-
A.
typicalTrigger
chosen
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
-
D.
oftenTargetedBy
Indicates that an entity is frequently chosen or subjected as the object of another entity’s actions, attention, or attacks.
-
E.
oftenFrom
Indicates that something frequently originates, derives, or comes from a particular source or location.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6b755c81909e9bd2a588c065b3 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.