Triple
T20585448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R136a1 |
E505773
|
entity |
| Predicate | expectedFate |
P24728
|
FINISHED |
| Object | core-collapse supernova or hypernova |
—
|
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: core-collapse supernova or hypernova | Statement: [R136a1, expectedFate, core-collapse supernova or hypernova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedFate Context triple: [R136a1, expectedFate, core-collapse supernova or hypernova]
-
A.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
B.
hasUncertainFate
Indicates that the outcome, status, or future of the related entity or event is unknown, unresolved, or not clearly determined.
-
C.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
D.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
E.
eschatologicalDestiny
Indicates the ultimate fate or final outcome that is believed to await an entity within a religious or philosophical view of the end times.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a976bca4819086a4949e299159b5 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.