Triple
T2721310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Ring Nebula |
E60084
|
entity |
| Predicate | progenitorStarType |
P39736
|
FINISHED |
| Object | Sun-like star |
—
|
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: Sun-like star | Statement: [Southern Ring Nebula, progenitorStarType, Sun-like star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progenitorStarType Context triple: [Southern Ring Nebula, progenitorStarType, Sun-like star]
-
A.
originalStar
chosen
Indicates that one entity is the initial or primary star from which another star or stellar object originates, is derived, or is otherwise based.
-
B.
stellarClass
Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
-
C.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
D.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
E.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
- 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.