Triple
T2721308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Ring Nebula |
E60084
|
entity |
| Predicate | centralStarType |
P9991
|
FINISHED |
| Object | white dwarf |
—
|
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: white dwarf | Statement: [Southern Ring Nebula, centralStarType, white dwarf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralStarType Context triple: [Southern Ring Nebula, centralStarType, white dwarf]
-
A.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
B.
starSystem
Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
-
C.
stellarClass
Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
-
D.
astronomicalType
chosen
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
E.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab1cb808190b0789c76bc9cb090 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.