Triple
T18887510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 1 |
E461993
|
entity |
| Predicate | supernovaExplosionYear |
P60198
|
FINISHED |
| Object | 1054 |
—
|
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: 1054 | Statement: [Messier 1, supernovaExplosionYear, 1054]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supernovaExplosionYear Context triple: [Messier 1, supernovaExplosionYear, 1054]
-
A.
supernovaTypeObserved
Indicates that a specific type or classification of supernova has been observed for an astronomical event.
-
B.
supernovaRecorded
Indicates that an occurrence of a supernova has been observed and documented in some form of record.
-
C.
supernovaTimescaleEstimate
Indicates an estimated duration or characteristic timescale associated with a supernova event.
-
D.
hasSupernovaRemnant
Indicates that an astronomical object is associated with or gives rise to a specific supernova remnant.
-
E.
explosionDateApprox
chosen
Indicates that an explosion occurred on or around a specified date, where the exact date is not known or is only approximate.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c4777434819098850da0ee1c6b43 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.