Triple
T3628676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Energy Survey |
E76900
|
entity |
| Predicate | supernovaFields |
P49645
|
FINISHED |
| Object | 10 fields |
—
|
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: 10 fields | Statement: [Dark Energy Survey, supernovaFields, 10 fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supernovaFields Context triple: [Dark Energy Survey, supernovaFields, 10 fields]
-
A.
hasSupernovaRemnant
Indicates that an astronomical object is associated with or gives rise to a specific supernova remnant.
-
B.
associatedNebula
Indicates a relationship where an object or entity is linked or connected to a particular nebula in some relevant way.
-
C.
stellarClass
Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
-
D.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
E.
astronomicalIdentity
Indicates that two astronomical entities are in fact the same object or refer to the same celestial body, despite possibly having different names or identifiers.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2df2b708190afef6925a53ec551 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.