Triple
T5775397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alnilam |
E127427
|
entity |
| Predicate | willEndAs |
P6078
|
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: [Alnilam, willEndAs, core-collapse supernova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willEndAs Context triple: [Alnilam, willEndAs, core-collapse supernova]
-
A.
will
chosen
Indicates that an entity is going to perform an action or be in a certain state in the future.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
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.
-
E.
canConclude
Indicates that one entity is able to logically derive or reach a conclusion about another entity or situation.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.