Triple
T21044342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Canis Majoris |
E518409
|
entity |
| Predicate | isLikelyToEndAs |
P142594
|
FINISHED |
| Object | core-collapse supernova |
—
|
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 | Statement: [Eta Canis Majoris, isLikelyToEndAs, core-collapse supernova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLikelyToEndAs Context triple: [Eta Canis Majoris, isLikelyToEndAs, core-collapse supernova]
-
A.
canBeConcludedWith
Indicates that one situation, process, or sequence is able to be finished, resolved, or brought to an end by another specified action or condition.
-
B.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
C.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
-
D.
canConclude
Indicates that one entity is able to logically derive or reach a conclusion about another entity or situation.
-
E.
isHomeEndFor
Indicates that something serves as the final destination, endpoint, or concluding location for a journey, process, or sequence.
- F. None of above. chosen
Provenance (4 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf2fc4881909b9e3400864e6b82 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:24 p.m.