Triple
T21355102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4536 |
E526597
|
entity |
| Predicate | hasSupernovaeObserved |
P132079
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NGC 4536, hasSupernovaeObserved, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupernovaeObserved Context triple: [NGC 4536, hasSupernovaeObserved, yes]
-
A.
supernovaTypeObserved
Indicates that a specific type or classification of supernova has been observed for an astronomical event.
-
B.
hasSupernovaRemnant
Indicates that an astronomical object is associated with or gives rise to a specific supernova remnant.
-
C.
hasSupernova
chosen
Indicates that a celestial object or region has experienced, is experiencing, or is associated with a supernova event.
-
D.
supernovaRecorded
Indicates that an occurrence of a supernova has been observed and documented in some form of record.
-
E.
supernovaVisibleToNakedEyeFor
Indicates that a supernova event was bright enough to be seen without optical instruments by a specified observer or at a specified location for a given duration.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8af9be3a48190aa8e6e9a5b812981 |
completed | April 22, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:06 p.m.