Triple
T19261775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UY Scuti |
E481664
|
entity |
| Predicate | likelyFuture |
P135330
|
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: [UY Scuti, likelyFuture, core-collapse supernova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyFuture Context triple: [UY Scuti, likelyFuture, core-collapse supernova]
-
A.
likelyBehavior
Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
-
B.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
-
C.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
D.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
E.
laterBelief
Indicates that an agent holds a particular belief at a time that is later than some referenced earlier time or belief state.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:28 p.m.