Triple
T5958642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betelgeuse |
E132578
|
entity |
| Predicate | massLossRate |
P67065
|
FINISHED |
| Object | about 1–2 × 10⁻⁶ solar masses per year |
—
|
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: about 1–2 × 10⁻⁶ solar masses per year | Statement: [Betelgeuse, massLossRate, about 1–2 × 10⁻⁶ solar masses per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massLossRate Context triple: [Betelgeuse, massLossRate, about 1–2 × 10⁻⁶ solar masses per year]
-
A.
massToLightRatio
Indicates the relationship between an object's total mass and its luminosity, expressing how much mass corresponds to each unit of emitted light.
-
B.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
C.
dynamicalMass_solarMasses
Indicates the dynamical mass of an object or system expressed in units of the Sun’s mass.
-
D.
massOfCentralBlackHole
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
E.
stellarMass_solarMasses
Indicates the mass of a star expressed as a multiple of the Sun’s mass.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:02 p.m.