Triple
T5089030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubecula Minor |
E114708
|
entity |
| Predicate | hasStellarMass |
P22644
|
FINISHED |
| Object | on the order of 10^9 solar masses |
—
|
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: on the order of 10^9 solar masses | Statement: [Nubecula Minor, hasStellarMass, on the order of 10^9 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarMass Context triple: [Nubecula Minor, hasStellarMass, on the order of 10^9 solar masses]
-
A.
stellarMass
chosen
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
B.
hasStarFormationMode
Indicates the specific manner or process by which star formation occurs in a given astronomical system or region.
-
C.
stellarMass_solarMasses
Indicates the mass of a star expressed as a multiple of the Sun’s mass.
-
D.
hasSupermassiveBlackHole
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
E.
isNonStarformingGalaxy
Indicates that a galaxy does not currently form new stars or has an extremely low rate of star formation.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd753f6544819090c028b34ee87536 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.