Triple
T4943458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SN 1987A |
E110990
|
entity |
| Predicate | shockInteractionWith |
P3970
|
FINISHED |
| Object | circumstellar ring |
—
|
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: circumstellar ring | Statement: [SN 1987A, shockInteractionWith, circumstellar ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shockInteractionWith Context triple: [SN 1987A, shockInteractionWith, circumstellar ring]
-
A.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
B.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
C.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
D.
hasForcesInvolved
Indicates that specific forces, such as military or organizational units, participate in or are engaged in a particular event or operation.
-
E.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.