Triple
T15581902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type Ia supernovae |
E374518
|
entity |
| Predicate | typicalExplosionEnergy |
P25889
|
FINISHED |
| Object | about 10^51 ergs |
—
|
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: about 10^51 ergs | Statement: [Type Ia supernovae, typicalExplosionEnergy, about 10^51 ergs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExplosionEnergy Context triple: [Type Ia supernovae, typicalExplosionEnergy, about 10^51 ergs]
-
A.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
explosiveYieldApprox
chosen
Indicates that one entity has an approximate explosive yield value, typically expressing the estimated magnitude of an explosion or explosive device.
-
C.
numberOfExplosions
Indicates the count of distinct explosion events associated with an entity or situation.
-
D.
fireballExplosionPower
Indicates the magnitude or intensity of an explosion produced by a fireball.
-
E.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e45ee3c8190a6aee06a5805ca39 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.