Triple
T12175782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolf–Rayet star |
E290082
|
entity |
| Predicate | hasMassLossRate |
P67065
|
FINISHED |
| Object | 10^-5 to 10^-4 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: 10^-5 to 10^-4 solar masses per year | Statement: [Wolf–Rayet star, hasMassLossRate, 10^-5 to 10^-4 solar masses per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassLossRate Context triple: [Wolf–Rayet star, hasMassLossRate, 10^-5 to 10^-4 solar masses per year]
-
A.
hasMassLoss
Indicates that an entity undergoes a reduction in its mass over time or as a result of some process or interaction.
-
B.
massLossRate
chosen
Indicates the rate at which an object or system is losing mass over time.
-
C.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
D.
massToLightRatio
Indicates the relationship between an object's total mass and its luminosity, expressing how much mass corresponds to each unit of emitted light.
-
E.
hasMassFraction
Indicates that a specified portion of a substance’s total mass is attributable to a particular component or constituent.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.